Re: 2.1.117 NFS Oops

Andrea Arcangeli (arcangeli@mbox.queen.it)
Sun, 23 Aug 1998 21:22:26 +0200 (CEST)

>> looks like someone clears the inode pointer stored in req->wb_inode
>> during the schedule()? Thus the reference to the inode in the
>> NFS_CLIENT macro will reference a bogus NULL pointer.

Exactly. req->wb_inode is NULL after the schedule().

Is this bug just been fixed right? If not I can try to find it since I am
able to reproduce the Oops with 2.1.117 recompiling the kernel via NFS
while cron.daily is running.

Andrea[s] Arcangeli

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html