[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140924131947.bc083e7f34981bbf73a364f1@linux-foundation.org>
Date: Wed, 24 Sep 2014 13:19:47 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jan Kara <jack@...e.cz>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Heinrich Schuchardt <xypron.debian@....de>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>,
Eric Paris <eparis@...isplace.org>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Pavel Emelyanov <xemul@...allels.com>,
Andrey Vagin <avagin@...nvz.org>
Subject: Re: [PATCH] fs: don't remove inotify watchers from alive inode-s
(v2)
On Wed, 24 Sep 2014 12:51:55 +0200 Jan Kara <jack@...e.cz> wrote:
> Hello,
>
> Andrew, what do you think about the patch below? Al objected that it
> changes userspace visible behavior some time ago and then he didn't react
> to our explanations...
Difficult situation. There's some really important information missing
from the changelog:
- Who cares? Is there some real application which is hurting from
the current situation? If so, who, what, how and why. If not, then
why change anything?
- A description of the userspace API change impact. How did the
interface change? What is the risk of this change causing damage to
real applications?
If we can answer these questions then we're in a position to make the
pain-versus-gain tradeoff decision.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists