From: Dave Hansen <dave@sr71.net>
To: dave@sr71.net
Cc: dave.hansen@linux.intel.com, avagin@gmail.com,
akpm@linux-foundation.org, gorcunov@openvz.org,
xemul@parallels.com, eparis@redhat.com, john@johnmccutchan.com,
rlove@rlove.org, linux-kernel@vger.kernel.org
Subject: [PATCH] inotify: hide internal kernel bits from fdinfo
Date: Mon, 21 Sep 2015 11:45:01 -0700 [thread overview]
Message-ID: <20150921184501.E0313E5A@viggo.jf.intel.com> (raw)
From: Dave Hansen <dave.hansen@linux.intel.com>
There was a report that my patch:
inotify: actually check for invalid bits in sys_inotify_add_watch()
broke CRIU.
The reason is that CRIU looks up raw flags in /proc/$pid/fdinfo/*
to figure out how to rebuild inotify watches and then passes those
flags directly back in to the inotify API. One of those flags
(FS_EVENT_ON_CHILD) is set in mark->mask, but is not part of the
inotify API. It is used inside the kernel to _implement_ inotify
but it is not and has never been part of the API.
My patch above ensured that we only allow bits which are part of
the API (IN_ALL_EVENTS). This broke CRIU.
FS_EVENT_ON_CHILD is really internal to the kernel. It is set
_anyway_ on all inotify marks. So, CRIU was really just trying
to set a bit that was already set.
This patch hides that bit from fdinfo. CRIU will not see the
bit, not try to set it, and should work as before. We should not
have been exposing this bit in the first place, so this is a good
patch independent of the CRIU problem.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Reported-by: Andrey Wagin <avagin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: xemul@parallels.com
Cc: Eric Paris <eparis@redhat.com>
Cc: john@johnmccutchan.com
Cc: rlove@rlove.org
Cc: linux-kernel@vger.kernel.org
---
b/fs/notify/fdinfo.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff -puN fs/notify/fdinfo.c~fdinfo-mask fs/notify/fdinfo.c
--- a/fs/notify/fdinfo.c~fdinfo-mask 2015-09-21 10:24:01.031864268 -0700
+++ b/fs/notify/fdinfo.c 2015-09-21 10:25:04.335723826 -0700
@@ -82,9 +82,16 @@ static void inotify_fdinfo(struct seq_fi
inode_mark = container_of(mark, struct inotify_inode_mark, fsn_mark);
inode = igrab(mark->inode);
if (inode) {
+ /*
+ * IN_ALL_EVENTS represents all of the mask bits
+ * that we expose to userspace. There is at
+ * least one bit (FS_EVENT_ON_CHILD) which is
+ * used only internally to the kernel.
+ */
+ u32 mask = mark->mask & IN_ALL_EVENTS;
seq_printf(m, "inotify wd:%x ino:%lx sdev:%x mask:%x ignored_mask:%x ",
inode_mark->wd, inode->i_ino, inode->i_sb->s_dev,
- mark->mask, mark->ignored_mask);
+ mask, mark->ignored_mask);
show_mark_fhandle(m, inode);
seq_putc(m, '\n');
iput(inode);
_
next reply other threads:[~2015-09-21 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 18:45 Dave Hansen [this message]
2015-09-21 19:26 ` [PATCH] inotify: hide internal kernel bits from fdinfo Eric Paris
2015-09-21 19:28 ` Cyrill Gorcunov
2015-09-21 19:56 ` Andrey Wagin
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=20150921184501.E0313E5A@viggo.jf.intel.com \
--to=dave@sr71.net \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=eparis@redhat.com \
--cc=gorcunov@openvz.org \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=xemul@parallels.com \
/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