All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 19 Jun 2002 19:48:17 +0200	[thread overview]
Message-ID: <20020619194817.J29373@suse.de> (raw)
In-Reply-To: <20020619124252.V4360-100000@abbey.hauschen>; from busterb@mail.utexas.edu on Wed, Jun 19, 2002 at 12:45:31PM -0500

On Wed, Jun 19, 2002 at 12:45:31PM -0500, Brent Cook wrote:

 > You were right. Backing out READDIRPLUS fixes the problem with NFS and
 > files losing the executable bit. I just tried things with 2.5.23-dj1 and
 > all is well.

Excellent, thanks for testing..

 > Here are a couple of compile fixes for that kernel though:

Thanks, added to the pending queue with the others

    Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-06-19 17:48 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
2002-06-19 17:45           ` Brent Cook
2002-06-19 17:48             ` Dave Jones [this message]
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=20020619194817.J29373@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 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.