mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Herbert Pötzl" <herbert@13thfloor.at>
To: Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Bind Mount Extensions 0.03 for 2.4/2.6
Date: Sat, 9 Aug 2003 19:15:35 +0200	[thread overview]
Message-ID: <20030809171535.GA10333@www.13thfloor.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]


Bind Mount Extensions 0.03 for 2.4/2.6

this should complete the RO aspects of --bind mounts, 
except for update_atime() and the Intermezzo stuff, 
(which I will add later on, if required ...), for 
linux 2.4.22-rc2 and 2.6.0-test3 ...

it should now handle the following cases as expected:

 - open (read/write/trunc), create
 - link, symlink, unlink
 - mknod (reg/block/char/fifo), mkfifo
 - mkdir, rmdir
 - (f)chown, (f)chmod, utimes
 - ioctl (gen/ext2/ext3/reiser)
 - access, truncate

please could you have a look at the patches, and 
give some response what would be required to get
this stuff into mainline ... TIA

(let me know if you would like to receive them
 in another form, e.g. not as attachment ;)

regarding update_atime(), I didn't do that one, 
because I (finally) read your mail about --bind
extensions and do not understand why you would
like to propagate vfsmount _and_ dentry to the
update_atime() function.

TIA,
Herbert


[-- Attachment #2: patch-2.4.22-rc2-bme0.03.diff.bz2 --]
[-- Type: application/octet-stream, Size: 3359 bytes --]

[-- Attachment #3: patch-2.6.0-test3-bme0.03.diff.bz2 --]
[-- Type: application/octet-stream, Size: 3598 bytes --]

                 reply	other threads:[~2003-08-09 17:18 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=20030809171535.GA10333@www.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.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

all inboxes | Powered by JetHome®