From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5 3/4] fs: handle potential filesystems which use I_DONTCACHE and drop the lock in ->drop_inode
Date: Fri, 10 Apr 2026 11:41:08 +0200 [thread overview]
Message-ID: <20260410-schiffen-abbuchung-1383b7b048f3@brauner> (raw)
In-Reply-To: <CAGudoHHeRPm+yZo7AVvadkZg5HNEKx6JPBBNQu0UPecJf2H7hw@mail.gmail.com>
On Thu, Apr 09, 2026 at 04:55:52PM +0200, Mateusz Guzik wrote:
> On Thu, Apr 9, 2026 at 3:40 PM Christian Brauner <brauner@kernel.org> wrote:
> >
> > On Wed, Apr 01, 2026 at 08:50:39PM +0200, Mateusz Guzik wrote:
> > > On Wed, Apr 1, 2026 at 7:45 PM Jan Kara <jack@suse.cz> wrote:
> > > >
> > > > On Tue 31-03-26 18:08:50, Mateusz Guzik wrote:
> > > > > f2fs and ntfs play games where they transitioning the refcount 0->1 and release
> > > >
> > > > I don't see ntfs providing .drop_inode at all in current Linu's kernel? The
> > > > f2fs case is indeed ugly and a gross hack. But I don't see easy way how to
> > > > fix that for now.
> > > >
> > >
> > > This was generated against next-20260327, then:
> >
> > Ideally don't develop against next... If you already know you're going
> > to do a bunch of work in an area. I can just assign you a branch to work
> > of off. Easier for everyone. Also makes the CI easier.
>
> So what should stuff be generated against? fs-next? vfs.all?
Use vfs.all
next prev parent reply other threads:[~2026-04-10 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:08 [PATCH v5 0/4] assorted ->i_count changes + extension of lockless handling Mateusz Guzik
2026-03-31 16:08 ` [PATCH v5 1/4] fs: add icount_read_once() and stop open-coding ->i_count loads Mateusz Guzik
2026-04-01 17:29 ` Jan Kara
2026-03-31 16:08 ` [PATCH v5 2/4] fs: relocate and tidy up ihold() Mateusz Guzik
2026-04-01 17:28 ` Jan Kara
2026-03-31 16:08 ` [PATCH v5 3/4] fs: handle potential filesystems which use I_DONTCACHE and drop the lock in ->drop_inode Mateusz Guzik
2026-04-01 17:45 ` Jan Kara
2026-04-01 18:50 ` Mateusz Guzik
2026-04-09 13:40 ` Christian Brauner
2026-04-09 14:55 ` Mateusz Guzik
2026-04-10 9:41 ` Christian Brauner [this message]
2026-03-31 16:08 ` [PATCH v5 4/4] fs: allow lockless ->i_count bumps as long as it does not transition 0->1 Mateusz Guzik
2026-04-08 17:01 ` Jan Kara
2026-04-18 12:32 ` Mateusz Guzik
2026-04-20 7:56 ` Jan Kara
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=20260410-schiffen-abbuchung-1383b7b048f3@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®