Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Jeff Layton <jlayton@kernel.org>,
	 Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC v2 4/6] inode: port __I_NEW to var event
Date: Fri, 23 Aug 2024 13:07:35 +0200	[thread overview]
Message-ID: <20240823-fanpost-ableisten-33928d6abf9d@brauner> (raw)
In-Reply-To: <20240823-bersten-besiedeln-d19f7547ad7a@brauner>

On Fri, Aug 23, 2024 at 10:20:31AM GMT, Christian Brauner wrote:
> On Fri, Aug 23, 2024 at 10:31:55AM GMT, NeilBrown wrote:
> > On Thu, 22 Aug 2024, Christian Brauner wrote:
> > > Port the __I_NEW mechanism to use the new var event mechanism.
> > > 
> > > Signed-off-by: Christian Brauner <brauner@kernel.org>
> > > ---
> > >  fs/bcachefs/fs.c          | 10 ++++++----
> > >  fs/dcache.c               |  3 +--
> > >  fs/inode.c                | 18 ++++++++----------
> > >  include/linux/writeback.h |  3 ++-
> > >  4 files changed, 17 insertions(+), 17 deletions(-)
> > > 
> > > diff --git a/fs/bcachefs/fs.c b/fs/bcachefs/fs.c
> > > index 94c392abef65..c0900c0c0f8a 100644
> > > --- a/fs/bcachefs/fs.c
> > > +++ b/fs/bcachefs/fs.c
> > > @@ -1644,14 +1644,16 @@ void bch2_evict_subvolume_inodes(struct bch_fs *c, snapshot_id_list *s)
> > >  				break;
> > >  			}
> > >  		} else if (clean_pass && this_pass_clean) {
> > > -			wait_queue_head_t *wq = bit_waitqueue(&inode->v.i_state, __I_NEW);
> > > -			DEFINE_WAIT_BIT(wait, &inode->v.i_state, __I_NEW);
> > > +			struct wait_bit_queue_entry wqe;
> > > +			struct wait_queue_head *wq_head;
> > >  
> > > -			prepare_to_wait(wq, &wait.wq_entry, TASK_UNINTERRUPTIBLE);
> > > +			wq_head = inode_bit_waitqueue(&wqe, &inode->v, __I_NEW);
> > 
> > I don't think you EXPORT inode_bit_waitqueue() so you cannot use it in
> > this module.
> 
> I had already fixed that in-tree because I got a build failure on one of
> my test machines.
> 
> > 
> > And maybe it would be good to not export it so that this code can get
> > cleaned up.
> 
> Maybe but I prefer this just to be a follow-up. So that we get hung up

*don't

> on ever more details.

  reply	other threads:[~2024-08-23 11:07 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 15:47 [PATCH RFC v2 0/6] inode: turn i_state into u32 Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 1/6] fs: add i_state helpers Christian Brauner
2024-08-21 22:12   ` NeilBrown
2024-08-21 22:47     ` Linus Torvalds
2024-08-21 23:34     ` Dave Chinner
2024-08-23  0:08       ` NeilBrown
2024-08-22  8:27     ` Christian Brauner
2024-08-22  8:37       ` Linus Torvalds
2024-08-23  0:14       ` NeilBrown
2024-08-23  2:52         ` Linus Torvalds
2024-08-23  3:05           ` Linus Torvalds
2024-08-23  3:44             ` Linus Torvalds
2024-08-23  5:01           ` NeilBrown
2024-08-23 12:47           ` [PATCH v3 0/6] inode: turn i_state into u32 Christian Brauner
2024-08-23 12:47             ` [PATCH v3 1/6] fs: add i_state helpers Christian Brauner
2024-09-05 16:01               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 2/6] fs: reorder i_state bits Christian Brauner
2024-09-05 16:02               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 3/6] inode: port __I_SYNC to var event Christian Brauner
2024-09-05 16:02               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 4/6] inode: port __I_NEW " Christian Brauner
2024-09-06 13:30               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 5/6] inode: port __I_LRU_ISOLATING " Christian Brauner
2024-09-09  7:35               ` Jan Kara
2024-08-23 12:47             ` [PATCH v3 6/6] inode: make i_state a u32 Christian Brauner
2024-09-09  7:35               ` Jan Kara
2024-08-23 15:06             ` [PATCH v3 0/6] inode: turn i_state into u32 Josef Bacik
2024-08-21 22:28   ` [PATCH RFC v2 1/6] fs: add i_state helpers Dave Chinner
2024-08-21 22:53     ` Linus Torvalds
2024-08-21 15:47 ` [PATCH RFC v2 2/6] fs: reorder i_state bits Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 3/6] writeback: port __I_SYNC to var event Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 4/6] inode: port __I_NEW " Christian Brauner
2024-08-23  0:31   ` NeilBrown
2024-08-23  8:20     ` Christian Brauner
2024-08-23 11:07       ` Christian Brauner [this message]
2024-08-21 15:47 ` [PATCH RFC v2 5/6] inode: port __I_LRU_ISOLATING " Christian Brauner
2024-08-21 19:41   ` Jeff Layton
2024-08-22  8:53     ` Christian Brauner
2024-08-22  9:48       ` Mateusz Guzik
2024-08-22 11:10         ` Christian Brauner
2024-08-22 12:46           ` Mateusz Guzik
2024-08-23  0:36   ` NeilBrown
2024-08-23  2:24     ` Linus Torvalds
2024-08-23  8:29       ` Christian Brauner
2024-08-21 15:47 ` [PATCH RFC v2 6/6] inode: make i_state a u32 Christian Brauner
2024-08-21 21:03   ` Andreas Dilger
2024-08-22  8:31     ` Christian Brauner
2024-08-21 19:15 ` [PATCH RFC v2 0/6] inode: turn i_state into u32 Josef Bacik
2024-08-21 19:42 ` Jeff Layton

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=20240823-fanpost-ableisten-33928d6abf9d@brauner \
    --to=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@suse.de \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox