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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E341FC433EF for ; Fri, 11 Mar 2022 12:36:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345522AbiCKMhW (ORCPT ); Fri, 11 Mar 2022 07:37:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51040 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239437AbiCKMhW (ORCPT ); Fri, 11 Mar 2022 07:37:22 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id F24931B45E6 for ; Fri, 11 Mar 2022 04:36:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1647002178; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UKVzSKeZMycHkCzJ/H7Xt/yUOfRzsg+N9RfGNa9T9b4=; b=ihqEGKfY4zPT1zGVWPi1kPYDfbLRxA/n+pekUknx2qlJpV05i76zQcV29H3IQY3a7LPbBr 7ESmAERUsWjbHGXRbrvO0H9/00NX2wwFAQAckG0RyiGus4eaF4p/0g1b8jtqB5v8ZM8GkS jFObwohPaxyT1I5Pkzl/dJcIljIXqtg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-159-mt5AQL_AOreHGHjfKihEvw-1; Fri, 11 Mar 2022 07:36:14 -0500 X-MC-Unique: mt5AQL_AOreHGHjfKihEvw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BA90D801AFE; Fri, 11 Mar 2022 12:36:13 +0000 (UTC) Received: from horse.redhat.com (unknown [10.22.16.83]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9828E68D94; Fri, 11 Mar 2022 12:36:13 +0000 (UTC) Received: by horse.redhat.com (Postfix, from userid 10451) id 31DC7223A46; Fri, 11 Mar 2022 07:36:13 -0500 (EST) Date: Fri, 11 Mar 2022 07:36:13 -0500 From: Vivek Goyal To: Steve French Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel , LKML Subject: Re: [LSF/MM/BPF TOPIC] Enabling change notification for network and cluster fs Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, Feb 23, 2022 at 11:16:33PM -0600, Steve French wrote: > Currently only local events can be waited on with the current notify > kernel API since the requests to wait on these events is not passed to > the filesystem. Especially for network and cluster filesystems it is > important that they be told that applications want to be notified of > these file or directory change events. > > A few years ago, discussions began on the changes needed to enable > support for this. Would be timely to finish those discussions, as > waiting on file and directory change events to network mounts is very > common for other OS, and would be valuable for Linux to fix. If this topic gets selected for discussion, I will be interested in joining the conversation. Vivek > > -- > Thanks, > > Steve >