public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linux-kernel@vger.kernel.org
Subject: changed proc permissions in 2.4
Date: Wed, 7 Feb 2001 20:43:04 +0100	[thread overview]
Message-ID: <20010207204304.C457@suse.de> (raw)

Hi,

there seems to be a bug in the /proc permissions handling. What I need
is a proc mount in a build chroot. This build chroot should not change
the settings on the build host, therefore its mounted read only. This
was ok with 2.2 kernels.
The 2.4 kernel has appearently only one "handler" for the proc
permissions:

fig:~/lsof # cat /proc/mounts | grep proc
proc /proc proc ro 0 0
/proc/bus/usb /proc/bus/usb usbdevfs rw 0 0

fig:~/lsof # remount rw /proc/

fig:~/lsof # cat /proc/mounts | grep proc
proc /proc proc rw 0 0
/proc/bus/usb /proc/bus/usb usbdevfs rw 0 0

fig:~/lsof # mount -oro -n -tproc none proc 

fig:~/lsof # cat /proc/mounts | grep proc
proc /proc proc ro 0 0
/proc/bus/usb /proc/bus/usb usbdevfs rw 0 0
none /root/lsof/proc proc ro 0 0

fig:~/lsof # remount rw /proc/

fig:~/lsof # cat /proc/mounts | grep proc
proc /proc proc rw 0 0
/proc/bus/usb /proc/bus/usb usbdevfs rw 0 0
none /root/lsof/proc proc rw 0 0

fig:~/lsof # umount proc/

fig:~/lsof # mount -oro -n -tproc proc proc 

fig:~/lsof # cat /proc/mounts | grep proc
proc /proc proc ro 0 0
/proc/bus/usb /proc/bus/usb usbdevfs rw 0 0
proc /root/lsof/proc proc ro 0 0

fig:~/lsof # cat /proc/version 
Linux version 2.4.1-olaf-loop-nohighmem (root@mandarine) (gcc version
2.95.2 19991024 (release)) #1 Tue Feb 6 13:35:53 GMT 2001

this is the 2.2 test:
grapefruit:~ # mkdir blah
grapefruit:~ # cd blah/
grapefruit:~/blah # mkdir proc
grapefruit:~/blah # cat /proc/mounts | grep proc
proc /proc proc rw 0 0
grapefruit:~/blah # mount -oro -n -tproc none proc
grapefruit:~/blah # cat /proc/mounts | grep proc
proc /proc proc rw 0 0
none proc proc ro 0 0

grapefruit:~/blah # cat /proc/version 
Linux version 2.2.16 (root@PReP.suse.de) (gcc version 2.95.3 19991030
(prerelease/franzo/20000625)) #1 Thu Sep 28 08:48:06 GMT 2000


Is this the way it should be? 
The real problem is X, it tries to open /proc/bus/pci/*/* rw, that
fails, no devices detected. Its all on ppc, just in case that matters.



Gruss Olaf

-- 
 $ man clone

BUGS
       Main feature not yet implemented...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-02-07 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 19:43 Olaf Hering [this message]
2001-02-07 19:53 ` changed proc permissions in 2.4 Olaf Hering

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=20010207204304.C457@suse.de \
    --to=olh@suse.de \
    --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