From: hanasaki <hanasaki@hanaden.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.4] NFS unlocking operation accesses invalid file struct
Date: Tue, 09 Dec 2003 19:27:20 -0600 [thread overview]
Message-ID: <3FD67678.5050704@hanaden.com> (raw)
In-Reply-To: <200312101006.46157.mita@miraclelinux.com>
could this be related to the problem I had?
debian sarge nfs client on 2.4.23
debian sarge nfs server on 2.6test11 - rpc number erros and bad locks
Akinobu Mita wrote:
> Hello Trond,
>
> I apologize for the delay in responding.
>
> On Friday 28 November 2003 01:23, Trond Myklebust wrote:
>
>>So then the correct thing to do is indeed to wrap the call to
>>locks_unlock_delete() with an fget()/fput() pair, and then to remove
>>the test for fl_pid in locks_same_owner().
>>
>>We then need to fix lockd so that it generates correct fl_owners for
>>its locks...
>>
>>Let me see if I can get that right.
>>
>
>
> I looked at your patch carefully
> (http://www.fys.uio.no/~trondmy/src/Linux-2.4.x/2.4.23-rc1/linux-2.4.23-01-posix_race.dif)
> and I think it would fix the problem completely.
>
> Thanks,
>
> --
> Akinobu Mita
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-12-10 1:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 11:00 [BUG 2.4] NFS unlocking operation accesses invalid file struct Akinobu Mita
2003-11-26 0:35 ` Trond Myklebust
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 [this message]
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=3FD67678.5050704@hanaden.com \
--to=hanasaki@hanaden.com \
--cc=linux-kernel@vger.kernel.org \
/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