xfs
[Top] [All Lists]

Re: Still module problems

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Still module problems
From: "Peter T. Breuer" <ptb@xxxxxxxxxx>
Date: Wed, 7 Mar 2001 00:47:06 +0100 (MET)
Reply-to: ptb@xxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
"GCS wrote:"
> If someone has Debian, please contact me personally. I do not know why, but
> I still have unresolved symbols in all modules. I have deleted the kernel

I'm running on debian, but with the january patch against 2.4.0.

I would appreciate it if the patch were less invasive. Has this been
done?  Surely changing make_request's type is intrinsically a bad idea?
I agree that the implementation is clever - setting the bh argument null
signals the new make_request to use the remaining args, kiobuff and
friends, instead, so only kiobuff-aware code will make use of it.  But
in that case why not write a separate function?  The kernel has
provisions for overwriting make_request _cleanly_.

And surely kiobuff + sector + count should be passed as a single
struct?

What are the issues with respect to buffer locking that I see vaguely
referred to in the faq? I am running xfs atop raid1 atop a block
driver that talks to the net, and a local partition or logical volume. I
was seeing lockups when the net driver ran against localhost (i.e. like
a loopback device).

Peter


<Prev in Thread] Current Thread [Next in Thread>