From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f194.google.com ([209.85.215.194]:45707 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727541AbeJRT4o (ORCPT ); Thu, 18 Oct 2018 15:56:44 -0400 Received: by mail-pg1-f194.google.com with SMTP id s3-v6so877928pga.12 for ; Thu, 18 Oct 2018 04:56:02 -0700 (PDT) Date: Thu, 18 Oct 2018 22:55:55 +1100 From: Matthew Bobrowski To: Jan Kara Cc: amir73il@gmail.com, linux-api@vger.kernel.org, sgrubb@redhat.com, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH v5 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM Message-ID: <20181018115553.GA3620@workstation> References: <3cd20de9fcf1ffa3044b5e48d21a91f280094cf1.1539758834.git.mbobrowski@mbobrowski.org> <20181018092620.GM23493@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181018092620.GM23493@quack2.suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Oct 18, 2018 at 11:26:20AM +0200, Jan Kara wrote: > On Wed 17-10-18 20:05:37, Matthew Bobrowski wrote: > > diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h > > index 329ac6684326..96616651220c 100644 > > --- a/include/linux/fsnotify_backend.h > > +++ b/include/linux/fsnotify_backend.h > > @@ -44,8 +44,9 @@ > > #define FS_Q_OVERFLOW 0x00004000 /* Event queued overflowed */ > > #define FS_IN_IGNORED 0x00008000 /* last inotify event here */ > > > > -#define FS_OPEN_PERM 0x00010000 /* open event in an permission hook */ > > +#define FS_OPEN_PERM 0x00010000 /* open event in a permission hook */ > > This hunk would belong to patch 1 instead of this one. Strange and totally agree. I'm quite perplexed as to why this came through in like this in this particular patch. Something really weird must've happened when I was "amending" previously recommended updates. > > > #define FS_ACCESS_PERM 0x00020000 /* access event in a permissions hook */ > > +#define FS_OPEN_EXEC_PERM 0x00040000 /* open/exec in a permission hook */ > > > > #define FS_EXCL_UNLINK 0x04000000 /* do not send events if object is unlinked */ > > #define FS_ISDIR 0x40000000 /* event occurred against dir */ > > @@ -64,7 +65,7 @@ > > FS_CLOSE_WRITE | FS_CLOSE_NOWRITE | FS_OPEN |\ > > FS_MOVED_FROM | FS_MOVED_TO | FS_CREATE |\ > > FS_DELETE | FS_OPEN_PERM | FS_ACCESS_PERM |\ > > - FS_OPEN_EXEC) > > + FS_OPEN_EXEC | FS_OPEN_EXEC_PERM) > > > > #define FS_MOVE (FS_MOVED_FROM | FS_MOVED_TO) > > > > You seem to be missing an update of ALL_FSNOTIFY_PERM_EVENTS to also > include FS_OPEN_EXEC_PERM. Oh, yep! Thanks for pointing that out. > Otherwise the patch looks good to me. :-) -- Matthew Bobrowski