From: Rik Theys <Rik.Theys@esat.kuleuven.be>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: Open with O_CREAT flag set fails to open existing files on non writable directories
Date: Thu, 21 Apr 2011 09:24:54 +0200 [thread overview]
Message-ID: <4DAFDBC6.60700@esat.kuleuven.be> (raw)
In-Reply-To: 20110420152324.GB15919@fieldses.org
Hi,
>> The patch adds a conditional statement to check for create permissions
>> only if the file doesn't exist.
> That looks correct to me, thanks.
> It's a bad bug, but appears to be one we've lived with a long time, so
> I'm a bit up in the air whether to submit now for 2.6.39 or to queue up
> for 2.6.40.
As an administrator who is hit by this bug on a daily basis, I would
like it to reach 2.6.39. But as I filed the bug, I guess I'm biased :-).
Distributions would like to see this accepted upstream before they
consider backporting the fix to their current stable releases.
Regards,
Rik
next reply other threads:[~2011-04-21 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 7:24 Rik Theys [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-20 12:09 Open with O_CREAT flag set fails to open existing files on non writable directories Sachin Prabhu
2011-04-20 15:23 ` 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=4DAFDBC6.60700@esat.kuleuven.be \
--to=rik.theys@esat.kuleuven.be \
--cc=bfields@fieldses.org \
--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 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.