From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "M.H.VanLeeuwen" <vanl@megsinet.net>
Cc: neilb@cse.unsw.edu.au, linux-kernel@vger.kernel.org
Subject: kernel BUG at /usr/src/linux/include/linux/nfs_fs.h:167! - reproducible
Date: Mon, 18 Dec 2000 11:02:40 +0100 (CET) [thread overview]
Message-ID: <14909.57536.917716.473278@charged.uio.no> (raw)
In-Reply-To: <3A3BE424.4A7FB8D9@megsinet.net>
In-Reply-To: <3A3BE424.4A7FB8D9@megsinet.net>
>>>>> " " == M H VanLeeuwen <vanl@megsinet.net> writes:
> Trond, Neil I don't know if this is a loopback bug or an NFS
> bug but since nfs_fs.h was implicated so I thought one of you
> may be interested.
> Could you let me know if you know this problem has already been
> fixed or if you need more info.
Hi,
As far as I'm concerned, it's a loopback bug.
Somebody appears to be trying to copy a 'struct file' in the routine
'loop_set_fd'. This will cause havoc in any and all filesystems that
rely on f_ops->open() , f_ops->release() to maintain internal data.
In this case, it's the file's RPC authorizations, that are getting
garbage-collected from beneath you once the original struct file gets
fput() at the end of the routine.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-18 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 21:52 kernel BUG at /usr/src/linux/include/linux/nfs_fs.h:167! - reproducible M.H.VanLeeuwen
2000-12-18 10:02 ` Trond Myklebust [this message]
2000-12-18 11:26 ` Neil Brown
2000-12-18 11:49 ` Alexander Viro
2000-12-20 3:20 ` kernel BUG at /usr/src/linux/include/linux/nfs_fs.h:167! -reproducible M.H.VanLeeuwen
2001-01-03 2:48 ` Again, kernel BUG at /usr/src/linux/include/linux/nfs_fs.h:167! 2.4.0-prerelease M.H.VanLeeuwen
-- strict thread matches above, loose matches on Subject: below --
2000-12-18 14:57 kernel BUG at /usr/src/linux/include/linux/nfs_fs.h:167! - reproducible vanl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14909.57536.917716.473278@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=vanl@megsinet.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox