From: Jamie Lokier <jamie@shareable.org>
To: "Joseph D. Wagner" <theman@josephdwagner.info>
Cc: matthew@wil.cx, willy@debian.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/locks.c Partially fixes leases issue
Date: Thu, 4 Dec 2003 05:15:53 +0000 [thread overview]
Message-ID: <20031204051553.GG1216@mail.shareable.org> (raw)
In-Reply-To: <200312032149.21849.theman@josephdwagner.info>
Joseph D. Wagner wrote:
> On Thursday, December 4, 2003 8:55 am, Jamie Lokier wrote:
> > These two are so similar they can be merged; just don't test "arg".
>
> That's what I through at first, but since this is only a partial patch, and
> a future patch would need to run additional checks independent of any write
> leases, I figured that it would be easier for the next guy if it had its
> own section so the next guy would know where the patch goes and have an
> easier time figuring it out.
That's what a comment saying "FIXME: R_RDLCK is not implemented
properly; it's currently treated the same as F_WRLCK" prior to the
merged test would be good for.
Anyone able to implement F_RDLCK properly is not going to have a
hard time knowing where to put the code :) Creating an empty place
just in case someone may fill it in future is the same as "this
page is under construction" on a web site :) :)
> > I don't agree with this patch as it is because, as Sean Neakums
> > pointed out, there is actually a field `inode->i_writecount' which is
> > remarkeably appropriate.
[...]
>
> As I said, it's just a partial fix until someone does all that stuff you
> describe. I really don't know enough to do all that, at least not yet.
If you have the time, try my suggestion. It is not complicated and
will fix the feature properly - and you'll learn a lot!
> Are you saying my patch won't get in?
That's not my decision to make.
It probably should go in (with the simpler test and comment), as it's
a genuine bug fix.
I'm saying that F_RDLCK is presently useless because it's broken, so
no applications dare use it as intended, and your fix doesn't really
change that - it still isn't useful. I'm egging you on to do it properly :)
-- Jamie
next prev parent reply other threads:[~2003-12-04 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 11:48 [PATCH] fs/locks.c Partially fixes leases issue Joseph D. Wagner
2003-12-04 2:55 ` Jamie Lokier
2003-12-03 15:49 ` Joseph D. Wagner
2003-12-04 5:15 ` Jamie Lokier [this message]
2003-12-04 13:31 ` Matthew Wilcox
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=20031204051553.GG1216@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=theman@josephdwagner.info \
--cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.