From: Olaf Kirch <okir@suse.de>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix NFS IRIX compatibility braindamage
Date: Mon, 6 Jan 2003 20:50:22 +0100 [thread overview]
Message-ID: <20030106195021.GD8269@suse.de> (raw)
In-Reply-To: <20030106193320.GD16489@codemonkey.org.uk>
On Mon, Jan 06, 2003 at 07:33:20PM +0000, Dave Jones wrote:
> I'm going through the old 2.4 changelogs looking for bits that
> have been missed out, the little one liners have been going
> direct to Linus/maintainer, but here's the first one I'm
> unsure of..
>
> Any reason this is missing in 2.5 ?
I think I sent it to the NFS mailing list and forgot about it
afterwards.
The problem this patch tries to address is that the current code allows
diskless clients to chmod device files, even when the directory is
exported read-only.
Olaf
--
Olaf Kirch | Anyone who has had to work with X.509 has probably
okir@suse.de | experienced what can best be described as
---------------+ ISO water torture. -- Peter Gutmann
next prev parent reply other threads:[~2003-01-06 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200210291208.g9TC8s305165@hera.kernel.org>
2003-01-06 19:33 ` [PATCH] Fix NFS IRIX compatibility braindamage Dave Jones
2003-01-06 19:50 ` Olaf Kirch [this message]
2003-01-08 0:24 ` Neil Brown
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=20030106195021.GD8269@suse.de \
--to=okir@suse.de \
--cc=davej@codemonkey.org.uk \
--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