Re: [PATCH v2 07/16] fanotify: rename a misnamed constant

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2 07/16] fanotify: rename a misnamed constant
From: Christian Brauner <brauner@xxxxxxxxxx>
Date: Fri, 9 Aug 2024 13:41:32 +0200
Cc: kernel-team@xxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, jack@xxxxxxx, amir73il@xxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, gfs2@xxxxxxxxxxxxxxx, linux-bcachefs@xxxxxxxxxxxxxxx
In-reply-to: <5d8efd2bf048544e9dcc7bb00cb9013837e3db6c.1723144881.git.josef@toxicpanda.com>
References: <cover.1723144881.git.josef@toxicpanda.com> <5d8efd2bf048544e9dcc7bb00cb9013837e3db6c.1723144881.git.josef@toxicpanda.com>

On Thu, Aug 08, 2024 at 03:27:09PM GMT, Josef Bacik wrote:
> From: Amir Goldstein <amir73il@xxxxxxxxx>
> 
> FANOTIFY_PIDFD_INFO_HDR_LEN is not the length of the header.
> 
> Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx>
> ---

Should probably be routed separately?
Reviewed-by: Christian Brauner <brauner@xxxxxxxxxx>

References:
- [PATCH v2 00/16] fanotify: add pre-content hooks
  - From: Josef Bacik
- [PATCH v2 07/16] fanotify: rename a misnamed constant
  - From: Josef Bacik

Prev by Date: Re: [PATCH v2 13/16] fsnotify: generate pre-content permission event on page fault
Next by Date: Re: [PATCH v2 03/16] fsnotify: generate pre-content permission event on open
Previous by thread: [PATCH v2 07/16] fanotify: rename a misnamed constant
Next by thread: [PATCH v2 08/16] fanotify: report file range info with pre-content events
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux