mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Andrew Morton <akpm@osdl.org>,
	Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: [Patch 0/6] Bind Mount Extensions 0.06
Date: Tue, 22 Feb 2005 13:09:55 +0100	[thread overview]
Message-ID: <20050222120955.GA3682@mail.13thfloor.at> (raw)


Hi Andrew! Al! Folks!

The following set of patches extends the per device 
'noatime', 'nodiratime' and last but not least the 
'ro' (read only) mount option to the vfs --bind mounts, 
allowing them to behave like any other mount, by 
honoring those mount flags (which are silently ignored 
by the current implementation in 2.4.x and 2.6.x)   	

the patch makes the following syscall variations behave 
as expected:

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

an older version of this patch was included in 
2.6.0-test6-mm2, and v2.6.4-wolk2.0, the patches were
used by several people, without any issues ...

please consider inclusion (in -mm ?) and/or let me know
what needs to be changed to get this functionality into
mainline ...

patches are against 2.6.11-rc4 but they do apply fine
against 2.6.11-rc4-bk9 (so no modification required)

TIA,
Herbert

(all six patches are)

Signed-off-by: Herbert Pötzl <herbert@13thfloor.at>


             reply	other threads:[~2005-02-22 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 12:09 Herbert Poetzl [this message]
2005-02-23  3:24 ` Matt Mackall
2005-02-23  3:51   ` Andrew Morton
2005-02-23  4:06     ` Matt Mackall
2005-02-24 21:04       ` Herbert Poetzl

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=20050222120955.GA3682@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=akpm@osdl.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®