From: Miklos Szeredi <mszeredi@suse.cz>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [NLM] 2.6.27 broken
Date: Mon, 09 Feb 2009 21:18:37 +0100 [thread overview]
Message-ID: <1234210717.4965.133.camel@tucsk> (raw)
In-Reply-To: <20090209181036.GI10297@fieldses.org>
On Mon, 2009-02-09 at 13:10 -0500, J. Bruce Fields wrote:
> On Fri, Feb 06, 2009 at 12:29:58PM +0100, Miklos Szeredi wrote:
> > On Thu, 2009-02-05 at 14:52 -0500, J. Bruce Fields wrote:
> > > On Thu, Feb 05, 2009 at 11:47:09AM +0100, Miklos Szeredi wrote:
> > > > But I think at least a comment in the code would be in order, or this
> > > > same mistake might be made again. Also I think the original code flow
> > > > is somewhat illogical.
> > >
> > > Yeah, I was literally just reverting the problematic lines of your
> > > previous commit. I'd rather keep it that way for now, just as a clear
> > > separation between the revert/bugfix and the cleanup.
> >
> > OK.
> >
> > > > How about this (it's essentially the same patch just a bit rearranged,
> > > > the authorship is still yours of course ;)
> > >
> > > ... but would happily queue up the cleanup for 2.6.30.
> >
> > Cool.
> >
> > > Actually, I find it strange to have just that single case which breaks,
> > > so that the code after the switch, which looks like it should be shared,
> > > actually just applies to one case. I'd be inclined to just suck
> > > everything up to "out:" into the -EAGAIN case and then make all cases
> > > "goto out" (or, equivalently, break).
> >
> > Yes, but it needs to be sucked into the FILE_LOCK_DEFERRED case as well.
> > It's just two lines and one of them is setting the error value, so it's
> > not real duplication.
>
> Whoops, right, missed that; so, I'm applying the below, sending the
> fixup in now, and queuing up the cleanup for 2.6.30 (with the blame
> assigned back to you, hah--object or have me add your signed-off-by).
No objections :)
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
BTW, one tip for stable patches: if you add a "Cc: stable@kernel.org"
line to the Signed-off-by block, then it will ease the patch's way into
the stable kernels as it will automatically be picked up by Greg's
scripts when it hits the mainline tree.
Thanks,
Miklos
next prev parent reply other threads:[~2009-02-09 20:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 13:28 [NLM] 2.6.27 broken Frank van Maarseveen
2008-11-20 22:27 ` J. Bruce Fields
2008-11-28 11:24 ` Frank van Maarseveen
2008-12-16 17:39 ` J. Bruce Fields
2008-12-16 19:43 ` Miklos Szeredi
2008-12-16 20:16 ` J. Bruce Fields
2009-02-04 23:33 ` J. Bruce Fields
2009-02-05 10:21 ` Frank van Maarseveen
2009-02-05 19:52 ` J. Bruce Fields
2009-02-05 10:47 ` Miklos Szeredi
2009-02-05 19:52 ` J. Bruce Fields
2009-02-06 11:29 ` Miklos Szeredi
2009-02-09 18:10 ` J. Bruce Fields
2009-02-09 20:18 ` Miklos Szeredi [this message]
2009-02-09 20:51 ` J. Bruce Fields
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=1234210717.4965.133.camel@tucsk \
--to=mszeredi@suse.cz \
--cc=bfields@fieldses.org \
--cc=frankvm@frankvm.com \
--cc=linux-nfs@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