From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH] fs: don't remove inotify watchers from alive inode-s (v2) Date: Wed, 24 Sep 2014 13:19:47 -0700 Message-ID: <20140924131947.bc083e7f34981bbf73a364f1@linux-foundation.org> References: <1411141516-1918-1-git-send-email-avagin@openvz.org> <20140924105155.GA24411@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Heinrich Schuchardt , "Michael Kerrisk (man-pages)" , Alexander Viro , John McCutchan , Robert Love , Eric Paris , Cyrill Gorcunov , Pavel Emelyanov , Andrey Vagin To: Jan Kara Return-path: In-Reply-To: <20140924105155.GA24411@quack.suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 24 Sep 2014 12:51:55 +0200 Jan Kara 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.