From: florin@iucha.net (Florin Iucha)
To: Neil Brown <neilb@suse.de>, Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-kernel@vger.kernel.org
Subject: REGRESSION: cannot change file access permissions on files NFS-mounted
Date: Sat, 5 May 2007 10:40:37 -0500 [thread overview]
Message-ID: <20070505154037.GA5459@iucha.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Hello,
This morning I updated the kernel on my workstation to the current git
tree (62ea6d80211ecc88ef516927ecebf64cb505be3f). Upon reboot, I
cannot change file access permissions of files in a directory that is
nfs mounted (using NFS4):
$ chmod 0600 $path
chmod: Changing permissions of `$path': Input/output error
In the kernel log I am getting these gems:
[ 275.990233] decode_attr_group: reply buffer overflowed in line
2678.<4>decode
_attr_group: reply buffer overflowed in line
2678.<4>decode_attr_group: reply bu
ffer overflowed in line 2678.<4>decode_attr_group: reply buffer
overflowed in li
ne 2678.<4>decode_attr_group: reply buffer overflowed in line
2678.<4>decode_att
r_group: reply buffer overflowed in line 2678.
The server is Linux running Debian testing with the kernel updated to
2.6.20-1-686 from
(http://ftp.us.debian.org/debian/pool/main/l/linux-2.6/linux-image-2.6.20-1-686_2.6.20-3_i386.deb)
Kernel 2.6.21 works fine on the client.
Cheers,
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-05-05 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 15:40 Florin Iucha [this message]
2007-05-06 19:53 ` REGRESSION: cannot change file access permissions on files NFS-mounted Marc Dietrich
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=20070505154037.GA5459@iucha.net \
--to=florin@iucha.net \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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