Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp5060775pxb; Thu, 14 Oct 2021 18:18:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzDmtWTFr0FpRmmPR64lZHGlhpdSVWVoIjj+Z1HQegWSlIXF+hZbEOyIgvVtu0uH60uo1X6 X-Received: by 2002:a05:6a00:1407:b0:44c:d2cc:916e with SMTP id l7-20020a056a00140700b0044cd2cc916emr8743386pfu.64.1634260718844; Thu, 14 Oct 2021 18:18:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634260718; cv=none; d=google.com; s=arc-20160816; b=o9p4qesk5SQviJgyhHA+Ko5hMv2b298Y+M23gPFC203FdyPiFEEVNJ8G7j2BeuH7mw HD8WzvFSNRgZDnDftR+OnbN2cdvN9V4QJYGMMUQTWcO2aYWBKHKKEDoB45ha0F0p080J 90BkjiIVP5dmlrOklnhxUJpuJVMakIz4zqD0dPVkVgmk37EQGm8Od/XyKcONV13ccfUd UKuKNI8q6iaROg8WV2NgaUwUpmeXrY+pR7Nr+4uDzSIffFT1yqHgF9lHdSSbSbH5cPzX GgreaDoAFvZ36BiDchf+EmITocLblSk4GMZWv+GMMOdpmavT44bCbTS4cMywOaMLUd78 vCBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=woSumkz2pXOx3vX0gqQ+b7sW/v8rJNtghKv96o4PjDA=; b=DapY5OshevI8P2sjTenUiFh2H9xegheejoKZffcrF3FplRZ+L233uGMMHWUMCr24Xs HXvt5rB+qHWysECTPIWZOpJjYP5l2WA2o+7XpBnMZI2CntukBzGVPmaK463/+vVOI5ga rPTsbMSI7VjeyowxoA7plHC+hzk1Rv4/urn/4+oqTblGdHGOC4X+KEA20zaC+31k7qJ2 7n2dBr2YUid55yUEXJwtk/e8ZEeofon2iky8nqq18z9cWUw0AJptuJ+lmBTT71ZJBp4N +ewS0JHKneYaE6jHvbD++/Ve9kFgFtAeg84CHfann1b4Iw78UC8PREaME6jbGgGFleM7 AWlA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m10si5684595pgv.643.2021.10.14.18.18.25; Thu, 14 Oct 2021 18:18:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232554AbhJNVj6 (ORCPT + 99 others); Thu, 14 Oct 2021 17:39:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53028 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232180AbhJNVj5 (ORCPT ); Thu, 14 Oct 2021 17:39:57 -0400 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A641BC061570; Thu, 14 Oct 2021 14:37:52 -0700 (PDT) Received: from localhost (unknown [IPv6:2804:14c:124:8a08::1007]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: krisman) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id 2A57B1F44F7B; Thu, 14 Oct 2021 22:37:50 +0100 (BST) From: Gabriel Krisman Bertazi To: jack@suse.com, amir73il@gmail.com Cc: djwong@kernel.org, tytso@mit.edu, dhowells@redhat.com, khazhy@google.com, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-api@vger.kernel.org, repnop@google.com, Gabriel Krisman Bertazi , kernel@collabora.com, Jan Kara Subject: [PATCH v7 07/28] inotify: Don't force FS_IN_IGNORED Date: Thu, 14 Oct 2021 18:36:25 -0300 Message-Id: <20211014213646.1139469-8-krisman@collabora.com> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20211014213646.1139469-1-krisman@collabora.com> References: <20211014213646.1139469-1-krisman@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org According to Amir: "FS_IN_IGNORED is completely internal to inotify and there is no need to set it in i_fsnotify_mask at all, so if we remove the bit from the output of inotify_arg_to_mask() no functionality will change and we will be able to overload the event bit for FS_ERROR." This is done in preparation to overload FS_ERROR with the notification mechanism in fanotify. Suggested-by: Amir Goldstein Reviewed-by: Amir Goldstein Reviewed-by: Jan Kara Signed-off-by: Gabriel Krisman Bertazi --- fs/notify/inotify/inotify_user.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/notify/inotify/inotify_user.c b/fs/notify/inotify/inotify_user.c index 62051247f6d2..29fca3284bb5 100644 --- a/fs/notify/inotify/inotify_user.c +++ b/fs/notify/inotify/inotify_user.c @@ -94,10 +94,10 @@ static inline __u32 inotify_arg_to_mask(struct inode *inode, u32 arg) __u32 mask; /* - * Everything should accept their own ignored and should receive events - * when the inode is unmounted. All directories care about children. + * Everything should receive events when the inode is unmounted. + * All directories care about children. */ - mask = (FS_IN_IGNORED | FS_UNMOUNT); + mask = (FS_UNMOUNT); if (S_ISDIR(inode->i_mode)) mask |= FS_EVENT_ON_CHILD; -- 2.33.0