All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
	 Josef Bacik <josef@toxicpanda.com>,
	kernel-team@fb.com, linux-fsdevel@vger.kernel.org, jack@suse.cz,
	 linux-xfs@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-mm@kvack.org,  linux-ext4@vger.kernel.org
Subject: Re: [PATCH v7 05/18] fsnotify: introduce pre-content permission events
Date: Wed, 20 Nov 2024 12:09:57 +0100	[thread overview]
Message-ID: <20241120-banditen-nimmersatt-e53c268d893a@brauner> (raw)
In-Reply-To: <CAHk-=wijFZtUxsunOVN5G+FMBJ+8A-+p5TOURv2h=rbtO44egw@mail.gmail.com>

> But if anybody is really worried about running out of f_mode bits, we
> could almost certainly turn the existing
> 
>         unsigned int f_flags;
> 
> into a bitfield, and make it be something like
> 
>         unsigned int f_flags:26, f_special:6;

I just saw this now. Two points I would like to keep you to keep mind.

I've already mentiond that I've freed up 5 fmode bits so it's not that
we're in immediate danger of running out. Especially since I added
f_ops_flags which contains all flags that are static, i.e., never change
and can simply live in the file operations struct and aren't that
performance sensitive.

I shrunk struct file to three cachelines. And in fact, we have 8 bytes
to use left since I removed f_version. So it really wouldn't be a
problem to simply add a separate u32 f_special member into struct file
without growing it and still leaving a 4 byte hole if it ever comes to
that.

  parent reply	other threads:[~2024-11-20 11:10 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 17:55 [PATCH v7 00/18] fanotify: add pre-content hooks Josef Bacik
2024-11-12 17:55 ` [PATCH v7 01/18] fsnotify: opt-in for permission events at file_open_perm() time Josef Bacik
2024-11-12 19:45   ` Linus Torvalds
2024-11-12 22:37     ` Amir Goldstein
2024-11-12 17:55 ` [PATCH v7 02/18] fanotify: don't skip extra event info if no info_mode is set Josef Bacik
2024-11-12 17:55 ` [PATCH v7 03/18] fanotify: rename a misnamed constant Josef Bacik
2024-11-12 17:55 ` [PATCH v7 04/18] fanotify: reserve event bit of deprecated FAN_DIR_MODIFY Josef Bacik
2024-11-12 17:55 ` [PATCH v7 05/18] fsnotify: introduce pre-content permission events Josef Bacik
2024-11-12 20:12   ` Linus Torvalds
2024-11-12 23:06     ` Amir Goldstein
2024-11-12 23:48       ` Linus Torvalds
2024-11-13  0:05         ` Amir Goldstein
2024-11-13 16:57           ` Linus Torvalds
2024-11-13 18:49             ` Amir Goldstein
2024-11-14 15:01               ` Jan Kara
2024-11-14 17:22                 ` Amir Goldstein
2024-11-13  0:12         ` Al Viro
2024-11-13  0:23           ` Linus Torvalds
2024-11-13  0:38             ` Linus Torvalds
2024-11-13  1:19               ` Al Viro
2024-11-13  4:30                 ` Al Viro
2024-11-13  8:50                   ` Amir Goldstein
2024-11-13 14:36                   ` Amir Goldstein
2024-11-13 20:31                     ` Al Viro
2024-11-13 10:10         ` Christian Brauner
2024-11-20 11:09         ` Christian Brauner [this message]
2024-11-20 11:36           ` Amir Goldstein
2024-11-13 19:11     ` Amir Goldstein
2024-11-13 21:22       ` Linus Torvalds
2024-11-13 22:35         ` Amir Goldstein
2024-11-13 23:07           ` Linus Torvalds
2024-11-12 17:55 ` [PATCH v7 06/18] fsnotify: pass optional file access range in pre-content event Josef Bacik
2024-11-12 17:55 ` [PATCH v7 07/18] fsnotify: generate pre-content permission event on open Josef Bacik
2024-11-12 19:54   ` Linus Torvalds
2024-11-12 23:40     ` Amir Goldstein
2024-11-13  0:58       ` Linus Torvalds
2024-11-13 10:12         ` Amir Goldstein
2024-11-12 17:55 ` [PATCH v7 08/18] fsnotify: generate pre-content permission event on truncate Josef Bacik
2024-11-12 17:55 ` [PATCH v7 09/18] fanotify: introduce FAN_PRE_ACCESS permission event Josef Bacik
2024-11-15 11:28   ` Amir Goldstein
2024-11-15 11:47     ` Jan Kara
2024-11-12 17:55 ` [PATCH v7 10/18] fanotify: report file range info with pre-content events Josef Bacik
2024-11-12 17:55 ` [PATCH v7 11/18] fanotify: allow to set errno in FAN_DENY permission response Josef Bacik
2024-11-12 17:55 ` [PATCH v7 12/18] fanotify: add a helper to check for pre content events Josef Bacik
2024-11-13 18:33   ` Amir Goldstein
2024-11-12 17:55 ` [PATCH v7 13/18] fanotify: disable readahead if we have pre-content watches Josef Bacik
2024-11-12 17:55 ` [PATCH v7 14/18] mm: don't allow huge faults for files with pre content watches Josef Bacik
2024-11-12 17:55 ` [PATCH v7 15/18] fsnotify: generate pre-content permission event on page fault Josef Bacik
2024-11-12 17:55 ` [PATCH v7 16/18] xfs: add pre-content fsnotify hook for write faults Josef Bacik
2024-11-12 17:55 ` [PATCH v7 17/18] btrfs: disable defrag on pre-content watched files Josef Bacik
2024-11-12 17:55 ` [PATCH v7 18/18] fs: enable pre-content events on supported file systems Josef Bacik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241120-banditen-nimmersatt-e53c268d893a@brauner \
    --to=brauner@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.