From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B587BC28CC1 for ; Wed, 29 May 2019 15:10:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 861DC23BAF for ; Wed, 29 May 2019 15:10:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559142659; bh=Mr53O7RleTzao/dC3tr4uYgD841gD6k8Bfp9NeUAZNk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=XIF+Xxayl7U+ekZgRcZioI87AUyPDC/2Q52vln4DNtPuMUo4C4I0QLA11CrYfgT5+ 9drB3DO6ktuUsDQHjN8hxkJKSi4fRgZTDD0qVejbKMa9Q5wa9sCzs0uKGi1h98ZZUR D1Lm3qv8xKDZHOV26X6aq+40F984GNNCrmuAprC8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726916AbfE2PKz (ORCPT ); Wed, 29 May 2019 11:10:55 -0400 Received: from mail.kernel.org ([198.145.29.99]:49632 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726489AbfE2PKz (ORCPT ); Wed, 29 May 2019 11:10:55 -0400 Received: from localhost (unknown [207.225.69.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2BD4C23B8C; Wed, 29 May 2019 15:10:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559142654; bh=Mr53O7RleTzao/dC3tr4uYgD841gD6k8Bfp9NeUAZNk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cyZDYlLhz99DlaSRHVOISk3X1d11X1h9Fiz3jTrszIeyByTGLo2bl0E7oNhgidbW/ VJ8N+GNkh9ZZy3qTa+Vmy92q5T2mmnFSfExvTgnpUfERO9Qe7mgd5l1GOtalC9z9xE RTTffwT/PNMfhmHHx+8OlwnVhmiphlqO2+oGPpvk= Date: Wed, 29 May 2019 08:10:53 -0700 From: Greg KH To: Jan Kara Cc: Amir Goldstein , David Howells , Al Viro , Ian Kent , linux-fsdevel , linux-api@vger.kernel.org, linux-block , keyrings@vger.kernel.org, LSM List , linux-kernel Subject: Re: [RFC][PATCH 0/7] Mount, FS, Block and Keyrings notifications Message-ID: <20190529151053.GA10231@kroah.com> References: <155905930702.7587.7100265859075976147.stgit@warthog.procyon.org.uk> <20190529142504.GC32147@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190529142504.GC32147@quack2.suse.cz> User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, May 29, 2019 at 04:25:04PM +0200, Jan Kara wrote: > > I am not asking that you implement fs_notify() before merging sb_notify() > > and I understand that you have a use case for sb_notify(). > > I am asking that you show me the path towards a unified API (how a > > typical program would look like), so that we know before merging your > > new API that it could be extended to accommodate fsnotify events > > where the final result will look wholesome to users. > > Are you sure we want to combine notification about file changes etc. with > administrator-type notifications about the filesystem? To me these two > sound like rather different (although sometimes related) things. This patchset is looking to create a "generic" kernel notification system, so I think the question is valid. It's up to the requestor to ask for the specific type of notification. thanks, greg k-h