From: Hugh Dickins <hughd@google.com>
To: Chuck Fox <cfox04@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
Jiri Slaby <jslaby@suse.cz>,
linux-mm@kvack.org
Subject: Re: TMPFS permissions bug in 2.6.35-rc3
Date: Mon, 21 Jun 2010 15:14:32 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.00.1006211457370.14654@tigran.mtv.corp.google.com> (raw)
In-Reply-To: <AANLkTilE0nMsbnkfaQM1vLrSaPeiv5ONgAftI51dQXHO@mail.gmail.com>
On Sun, 20 Jun 2010, Chuck Fox wrote:
>
> I've encountered a bug in 2.6.35-RC3 where my /tmp directory
> (mounted using tmpfs) returns a "File too large" error when adding
> execute privileges for the group permission byte:
> Example:
> touch /tmp/afile
> chmod 767 /tmp/afile # example where chmod works fine
> setting bits that are not the group execute bit
> chmod 755 /tmp/afile
> chmod: changing permissions of `/tmp/afile': File too large # bug
How very peculiar! Thank you for reporting it. I was about to suggest
some memory corruption must have occurred, but no....
>
> There are several gigabytes of free RAM + several more gigabytes of
> swap space available.
>
> Here's more information:
>
> Linux alpha1 2.6.35-rc3-next-20100614 #5 SMP Sun Jun 20 18:55:35 EDT
> 2010 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel
> GNU/Linux
> ...
... that's actually one of the linux-next kernels you're running there:
and I bet you'll find Jiri's patch below fixes your problem!
prev parent reply other threads:[~2010-06-21 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 0:52 Chuck Fox
2010-06-21 2:43 ` Chuck Fox
2010-06-21 22:14 ` Hugh Dickins [this message]
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=alpine.DEB.1.00.1006211457370.14654@tigran.mtv.corp.google.com \
--to=hughd@google.com \
--cc=cfox04@gmail.com \
--cc=hch@lst.de \
--cc=jslaby@suse.cz \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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