From: Dave Jones <davej@suse.de>
To: Brent Cook <busterb@mail.utexas.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File permission problem with NFSv3 and 2.5.20-dj4
Date: Sat, 15 Jun 2002 14:23:30 +0200 [thread overview]
Message-ID: <20020615142330.C16772@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0202072243560.26015-100000@Appserv.suse.de> <20020614171820.A13031-100000@abbey.hauschen>
On Fri, Jun 14, 2002 at 05:30:01PM -0500, Brent Cook wrote:
> Looks like there is a problem with NFSv3 and file permissions in the DJ
> kernels.
>
> A file that is marked as executable will lose its executable flag whenever
> it is written to. I suspect the proble lies in the changes to the NFS file
> info cacheing in the DJ kernels at least since 2.5.20-dj1 (I was unable
> to find where this change occured in the changelog).
The NFS changes need going over. I'll see whats left after backing out
Trond's READDIRPLUS patch. I'm expecting it to be just some small bits
like BKL shifting around, but that shouldn't be causing the problems
you saw..
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-15 12:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 3:52 Fix for duplicate /proc entries Brent Cook
2002-02-06 18:11 ` Dave Jones
2002-02-07 21:38 ` Brent Cook
2002-02-07 21:45 ` Dave Jones
2002-02-08 16:13 ` Brent Cook
2002-02-08 17:47 ` Mike Fedyk
2002-02-08 17:54 ` Alexander Viro
2002-02-08 18:12 ` Tommy Reynolds
2002-06-14 22:30 ` File permission problem with NFSv3 and 2.5.20-dj4 Brent Cook
2002-06-15 12:23 ` Dave Jones [this message]
2002-06-19 17:45 ` Brent Cook
2002-06-19 17:48 ` Dave Jones
2002-06-19 17:52 ` another sched.c error with athlon Kirk Reiser
2002-06-19 18:27 ` Adrian Bunk
2002-04-10 14:02 ` Mouse interrupts: the death knell of a VP6 Brent Cook
2002-04-10 15:23 ` Oleg Drokin
2002-04-10 16:43 ` Brent Cook
2002-04-10 16:49 ` William Park
2002-04-11 6:39 ` john slee
2002-04-10 20:55 ` Oleg Drokin
2002-04-10 17:16 ` John Adams
2002-04-10 17:52 ` Brent Cook
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=20020615142330.C16772@suse.de \
--to=davej@suse.de \
--cc=busterb@mail.utexas.edu \
--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