From: Miklos Szeredi <miklos@szeredi.hu>
To: viro@ZenIV.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jack@suse.cz, hch@infradead.org, akpm@linux-foundation.org,
toshi.okajima@jp.fujitsu.com, mszeredi@suse.cz
Subject: [PATCH v5 0/4] read-only remount race fix
Date: Wed, 3 Aug 2011 12:48:37 +0200 [thread overview]
Message-ID: <1312368521-7911-1-git-send-email-miklos@szeredi.hu> (raw)
Al,
Here's an update of the read-only remount race fixes.
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git read-only-remount-fixes.v5
Please apply.
Thanks,
Miklos
---
Miklos Szeredi (4):
vfs: ignore error on forced remount
vfs: keep list of mounts for each superblock
vfs: protect remounting superblock read-only
vfs: fs_may_remount_ro: turn unnecessary check into a WARN_ON
---
fs/file_table.c | 7 ++++-
fs/internal.h | 1 +
fs/namespace.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++-
fs/super.c | 27 +++++++++++++++++++++----
include/linux/fs.h | 4 +++
include/linux/mount.h | 1 +
6 files changed, 82 insertions(+), 8 deletions(-)
next reply other threads:[~2011-08-03 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 10:48 Miklos Szeredi [this message]
2011-08-03 10:48 ` [PATCH 1/4] vfs: ignore error on forced remount Miklos Szeredi
2011-08-03 10:49 ` Christoph Hellwig
2011-08-03 16:15 ` Miklos Szeredi
2011-08-03 10:48 ` [PATCH 2/4] vfs: keep list of mounts for each superblock Miklos Szeredi
2011-08-03 21:53 ` Christoph Hellwig
2011-08-03 22:17 ` Al Viro
2011-08-04 9:10 ` Miklos Szeredi
2011-08-04 9:46 ` Jan Kara
2011-08-04 9:58 ` Miklos Szeredi
2011-08-03 10:48 ` [PATCH 3/4] vfs: protect remounting superblock read-only Miklos Szeredi
2011-08-03 10:48 ` [PATCH 4/4] vfs: fs_may_remount_ro: turn unnecessary check into a WARN_ON Miklos Szeredi
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=1312368521-7911-1-git-send-email-miklos@szeredi.hu \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=toshi.okajima@jp.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).