From: Roman Mamedov <rm@romanrm.net>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit
Date: Tue, 25 Oct 2022 02:23:43 +0500 [thread overview]
Message-ID: <20221025022343.4d979cb3@nvm> (raw)
In-Reply-To: <20221024141629.GD5824@twin.jikos.cz>
On Mon, 24 Oct 2022 16:16:29 +0200
David Sterba <dsterba@suse.cz> wrote:
> > But not backported to stable series, why not? Seems to be a small and simple
> > fix.
>
> 5.10 may still be a reasonable target for backport. It does not apply
> cleanly and the 5.10 version tries to do some flushing of subvolume
> trees, which was removed later on, there may be some dependencies too.
Sorry I meant the longterm series. The issue was reported starting with
4.15-rc1, so of these also 4.19 and 5.4 will be affected. Sure, those may or
may not be as important or feasible for a backport, but at least 5.10
hopefully is, as it is the current long-longterm supported until 2026 per the
Releases page on kernel.org, 3 years further than 5.15.
--
With respect,
Roman
next prev parent reply other threads:[~2022-10-24 23:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 23:17 WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit Roman Mamedov
2022-10-24 7:37 ` Roman Mamedov
2022-10-24 14:16 ` David Sterba
2022-10-24 21:23 ` Roman Mamedov [this message]
2022-11-04 13:02 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2017-12-14 11:02 Dmitrii Tcvetkov
2017-12-14 13:21 ` Nikolay Borisov
2017-12-14 13:38 ` David Sterba
2017-12-14 15:05 ` Dmitrii Tcvetkov
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=20221025022343.4d979cb3@nvm \
--to=rm@romanrm.net \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.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.