From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Heinrich Schuchardt <xypron.debian@gmx.de>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Eric Paris <eparis@parisplace.org>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Pavel Emelyanov <xemul@parallels.com>,
Andrey Vagin <avagin@openvz.org>
Subject: Re: [PATCH] fs: don't remove inotify watchers from alive inode-s (v2)
Date: Thu, 2 Oct 2014 12:44:57 -0700 [thread overview]
Message-ID: <20141002124457.d1478b8aa91265e6ff171ab7@linux-foundation.org> (raw)
In-Reply-To: <20141002104552.GC19748@quack.suse.cz>
On Thu, 2 Oct 2014 12:45:52 +0200 Jan Kara <jack@suse.cz> wrote:
> > With the patch you'll always have the second case. So without the patch you
> > don't receive some events if the file has at least 2 hardlinks and then
> > gets unlinked. I think the risk that some application relies on *not* getting
> > those events is pretty low (especially since in the common case of file
> > without hardlinks you will get all those events).
> Ping Andrew? Do you still need more info or are you now OK to merge the
> patch?
Resend please, with a completed changelog.
prev parent reply other threads:[~2014-10-02 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 15:45 Andrey Vagin
2014-09-19 15:56 ` [PATCH] inotify.7: describe ambiguous behaviour of IN_DELETE_SELF Andrey Vagin
2014-09-19 16:15 ` [PATCH] fs: don't remove inotify watchers from alive inode-s (v2) Cyrill Gorcunov
2014-09-24 10:51 ` Jan Kara
2014-09-24 20:19 ` Andrew Morton
2014-09-25 8:30 ` Jan Kara
2014-09-25 20:38 ` Cyrill Gorcunov
2014-10-02 10:45 ` Jan Kara
2014-10-02 19:44 ` Andrew Morton [this message]
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=20141002124457.d1478b8aa91265e6ff171ab7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=eparis@parisplace.org \
--cc=gorcunov@openvz.org \
--cc=jack@suse.cz \
--cc=john@johnmccutchan.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rlove@rlove.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
--cc=xypron.debian@gmx.de \
/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
Powered by JetHome