linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: desrt <desrt@desrt.ca>
To: linux-kernel@vger.kernel.org
Subject: shmem_file_setup creating SYSV00000000 files in (ext3) root filesystem
Date: Fri, 05 Dec 2003 22:45:44 -0500	[thread overview]
Message-ID: <1070682344.17941.6.camel@peloton.desrt.ca> (raw)

kernel version is 2.4.23.

the problem is caused by the fact that the checks that shmem_file_setup
does to determine the location of the mountpoint of tmpfs fail to take
into account the effect of pivot_root.

that is: if i mount a tmpfs as /, then mount a ext3 filesystem and
pivot_root into it with put_old as, say, /var/tmp, then shmem_file_setup
will still think that the tmpfs is mounted at / (and as a result creates
shared memory files on the root filesystem instead of on /var/tmp as it
ought to)

i'm not actually sure what the code in mm/shmem.c:shmem_file_setup()
does, but i assume the problem is this line:
	        root = shm_mnt->mnt_root;

and somehow as a result, this happens:
peloton:/proc# grep deleted */maps
17923/maps:4201a000-4207a000 rw-s 00000000 00:04 21233690  
/SYSV00000000 (deleted)
17923/maps:424dd000-4253d000 rw-s 00000000 00:04 21266460  
/SYSV00000000 (deleted)
17926/maps:4201a000-4207a000 rw-s 00000000 00:04 21233690  
/SYSV00000000 (deleted)
17926/maps:424dd000-4253d000 rw-s 00000000 00:04 21266460  
/SYSV00000000 (deleted)
17927/maps:4201a000-4207a000 rw-s 00000000 00:04 21233690  
/SYSV00000000 (deleted)
[many many many lines follow]

if you have any advice or can confirm to me that this is actually a bug
in the kernel, please reply.  i'm not on the list.

thanks,
ryan.


             reply	other threads:[~2003-12-06  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  3:45 desrt [this message]
2003-12-12 12:50 ` shmem_file_setup creating SYSV00000000 files in (ext3) root filesystem Christoph Rohland

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=1070682344.17941.6.camel@peloton.desrt.ca \
    --to=desrt@desrt.ca \
    --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;
as well as URLs for NNTP newsgroup(s).