From: Chuck Fox <cfox04@gmail.com>
To: hughd@google.com
Cc: linux-mm@kvack.org
Subject: TMPFS permissions bug in 2.6.35-rc3
Date: Sun, 20 Jun 2010 20:52:54 -0400 [thread overview]
Message-ID: <AANLkTilE0nMsbnkfaQM1vLrSaPeiv5ONgAftI51dQXHO@mail.gmail.com> (raw)
Hugh & List:
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
There are several gigabytes of free RAM + several more gigabytes of
swap space available.
Here's more information:
scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
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
Gnu C 4.5.0
Gnu make 3.81
binutils 2.20.1.20100521
util-linux 2.17.2
mount support
module-init-tools 3.11.1
e2fsprogs 1.41.12
Linux C Library 2.12
Dynamic linker (ldd) 2.12
Linux C++ Library 6.0.14
Procps 3.2.8
Net-tools 1.60
Kbd 1.15.2
Sh-utils 8.5
Modules Loaded w83627ehf hwmon_vid coretemp
snd_hda_codec_analog nvidia snd_seq_dummy snd_seq_oss
snd_seq_midi_event snd_seq snd_seq_device tun snd_pcm_oss
snd_mixer_oss i2c_i801 sg snd_hda_intel snd_hda_codec snd_pcm
snd_page_alloc e1000e sky2
My fstab entries for mounting /dev/shm and for /tmp:
tmpfs /dev/shm tmpfs defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,nosuid,mode=1777 0 0
Let me know if there is anything else I can provide to help hunt down the bug!
P.S. --> I got your email from a list of kernel maintainers, if there
is another address this report should go to, please let me know & I'll
forward it.
--
Chuck Fox
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2010-06-21 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 0:52 Chuck Fox [this message]
2010-06-21 2:43 ` Chuck Fox
2010-06-21 22:14 ` Hugh Dickins
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=AANLkTilE0nMsbnkfaQM1vLrSaPeiv5ONgAftI51dQXHO@mail.gmail.com \
--to=cfox04@gmail.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.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