public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: linux-kernel@vger.kernel.org
Subject: hur hur.  fusexmp (userspace fs) + autofs + mount --rbind equals BLURP
Date: Wed, 22 Sep 2004 20:19:31 +0100	[thread overview]
Message-ID: <20040922191931.GD7308@lkcl.net> (raw)

anybody scared of ugly usage of linux kernel modules should look away,
_right_ now :)

... that having been said, this is quite a problem for mount --rbind.

repro setup:

1) install fuse.
2) install autofs.
3) write an /etc/autofs.media with a mountpoint /media/floppy
4) mkdir /mnt/test and run fusexmp /mnt/test &
5) mkdir /home/yourhome/media and mount --rbind /media /home/yourhome/media
6) attempt to access /mnt/test/home/yourhome/media/floppy

... and watch the little bits of kernel segfaults go _flying_ by...

this is with 2.6.8[.1-selinux1].

some clues as to there-might-be-a-problem-with-rbind are that the
problem does _not_ occur if you access /home/yourhome/media/floppy,
and a second clue is that if there are any subdirectories in /media
prior to running autofs, with a bit of dickering about with the
order of the above repro setup it's possible to _see_ those subdirectories
_even_ though you've done a mount --rbind.

i think i saw this occur when i swapped stages 4) and 5) above.

l.

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


                 reply	other threads:[~2004-09-22 19:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040922191931.GD7308@lkcl.net \
    --to=lkcl@lkcl.net \
    --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