From: akpm@linux-foundation.org
To: hansendc@us.ibm.com, haveblue@us.ibm.com, hch@lst.de,
miklos@szeredi.hu, viro@zeniv.linux.org.uk,
mm-commits@vger.kernel.org
Subject: - r-o-bind-mounts-elevate-writer-count-for-custom-struct_file.patch removed from -mm tree
Date: Thu, 15 Feb 2007 00:33:45 -0800 [thread overview]
Message-ID: <200702150833.l1F8XjTQ024664@shell0.pdx.osdl.net> (raw)
The patch titled
r/o bind mounts: elevate writer count for custom struct_file
has been removed from the -mm tree. Its filename was
r-o-bind-mounts-elevate-writer-count-for-custom-struct_file.patch
This patch was dropped because it had testing failures
------------------------------------------------------
Subject: r/o bind mounts: elevate writer count for custom struct_file
From: Dave Hansen <hansendc@us.ibm.com>
Some filesystems forego the use of normal vfs calls to create struct files.
Make sure that these users elevate the mnt writer count. These probably don't
have any real meaning because there is no real backing store for these mounts,
but it is here for consistency.
Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/file_table.c | 4 ++++
1 file changed, 4 insertions(+)
diff -puN fs/file_table.c~r-o-bind-mounts-elevate-writer-count-for-custom-struct_file fs/file_table.c
--- a/fs/file_table.c~r-o-bind-mounts-elevate-writer-count-for-custom-struct_file
+++ a/fs/file_table.c
@@ -170,6 +170,10 @@ int init_file(struct file *file, struct
file->f_mapping = dentry->d_inode->i_mapping;
file->f_mode = mode;
file->f_op = fop;
+ if (mode & FMODE_WRITE) {
+ error = mnt_want_write(mnt);
+ WARN_ON(error);
+ }
return error;
}
_
Patches currently in -mm which might be from hansendc@us.ibm.com are
r-o-bind-mounts-elevate-writer-count-for-custom-struct_file.patch
r-o-bind-mounts-remove-is_rdonly-from-permission.patch
r-o-bind-mounts-reiser4-remove-is_rdonly-checks.patch
next reply other threads:[~2007-02-15 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 8:33 akpm [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-14 18:53 - r-o-bind-mounts-elevate-writer-count-for-custom-struct_file.patch removed from -mm tree akpm
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=200702150833.l1F8XjTQ024664@shell0.pdx.osdl.net \
--to=akpm@linux-foundation.org \
--cc=hansendc@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mm-commits@vger.kernel.org \
--cc=viro@zeniv.linux.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.