From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.4] NFS unlocking operation accesses invalid file struct
Date: 25 Nov 2003 19:35:55 -0500 [thread overview]
Message-ID: <shs1xrwvudw.fsf@charged.uio.no> (raw)
In-Reply-To: <200311252000.32094.mita@miraclelinux.com>
>>>>> " " == Akinobu Mita <mita@miraclelinux.com> writes:
> Does anyone have a idea of how to fix it ?
Yes. I posted a patch about a week or 2 ago. The original patch can be
found on
http://www.fys.uio.no/~trondmy/src/Linux-2.4.x/2.4.23-rc1/linux-2.4.23-01-posix_race.dif
However, I now believe the real problem here is that
locks_remove_posix() should also be checking the pid (as is done in
all the other POSIX locking checks by calling locks_same_owner()).
It is wrong for locks_remove_posix() to be deleting locks that don't
belong to this pid... Note: this bug exists in 2.6.x. too, although
there it does not cause an Oops...
Cheers,
Trond
--- linux-2.4.23-rc1/fs/locks.c.orig 2003-11-16 19:30:53.000000000 -0500
+++ linux-2.4.23-rc1/fs/locks.c 2003-11-25 19:34:02.000000000 -0500
@@ -1746,7 +1746,8 @@
lock_kernel();
before = &inode->i_flock;
while ((fl = *before) != NULL) {
- if ((fl->fl_flags & FL_POSIX) && fl->fl_owner == owner) {
+ if ((fl->fl_flags & FL_POSIX) && fl->fl_owner == owner &&
+ fl->fl_pid == current->pid) {
locks_unlock_delete(before);
before = &inode->i_flock;
continue;
next prev parent reply other threads:[~2003-11-26 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 11:00 Akinobu Mita
2003-11-26 0:35 ` Trond Myklebust [this message]
2003-11-27 11:54 ` Akinobu Mita
2003-11-27 15:15 ` Gene Heskett
2003-11-27 16:23 ` Trond Myklebust
2003-12-10 1:06 ` Akinobu Mita
2003-12-10 1:27 ` hanasaki
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=shs1xrwvudw.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mita@miraclelinux.com \
/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
all inboxes | Powered by JetHome®