From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Naohiro Aota <naohiro.aota@wdc.com>,
linux-btrfs@vger.kernel.org,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH] btrfs: fix invalid mapping xarray state
Date: Tue, 13 Aug 2024 15:36:51 +0200 [thread overview]
Message-ID: <20240813133651.GR25962@twin.jikos.cz> (raw)
In-Reply-To: <9bedda40-76fc-427e-8cbc-dfa613dafa7e@gmx.com>
On Mon, Aug 12, 2024 at 02:47:04PM +0930, Qu Wenruo wrote:
>
>
> 在 2024/8/10 00:38, David Sterba 写道:
> > On Fri, Aug 09, 2024 at 04:54:22PM +0900, Naohiro Aota wrote:
> >>
> >> Reported-by: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> >> Fixes: 97713b1a2ced ("btrfs: do not clear page dirty inside extent_write_locked_range()")
> >
> > This is fixing a regression in 6.11 but the patch does not apply to
> > anything that could be used as a base branch (master, misc-6.11,
> > for-next).
> >
>
> Are you using a wrong branch?
>
> This patch can be applied without any conflict (although a typo, beging
> -> being) on for-next (89af55f1ed3d4354a629f08b87dfcafa3aabb90e).
>
> For upstream RCs, it's only conflicting with the recent change on the
> folio usage, only a `page_folio(page)`->`folio` change.
Yeah, now it applies to for-next cleanly and the page/folio is minor
conflict.
prev parent reply other threads:[~2024-08-13 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 7:54 [PATCH] btrfs: fix invalid mapping xarray state Naohiro Aota
2024-08-09 7:58 ` Qu Wenruo
2024-08-09 15:08 ` David Sterba
2024-08-12 5:17 ` Qu Wenruo
2024-08-13 13:36 ` David Sterba [this message]
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=20240813133651.GR25962@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=shinichiro.kawasaki@wdc.com \
/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.