From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>,
dsterba@suse.cz, quwenruo.btrfs@gmx.com,
linux-kernel@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: commit 108cc873398932af589c295f78c348513b8d70d9 breaks update-grub on btrfs root filesystem
Date: Fri, 11 Sep 2026 20:11:47 +0200 [thread overview]
Message-ID: <20260911181146.GD54722@twin.jikos.cz> (raw)
In-Reply-To: <9ca6e653-f89e-4ed2-8f97-783a5663f97c@suse.com>
On Thu, Sep 10, 2026 at 07:28:39AM +0930, Qu Wenruo wrote:
> 在 2026/9/9 23:48, Hanabishi 写道:
> > Hello.
> >
> > May I ask why you guys keep ignoring me completely?
>
> If you think we have time to reply every report, then just check how
> many syzbot reports are not addressed.
>
> > This is clearly a regression for userspace (see my previous reports).
>
> Unfortunately it's not.
Are we looking at the same reports??? "My system does not boot after
update" is a regression.
> The problem is there no matter if you have that patch.
>
> There are a lot of ways to make btrfs to report a weird device path even
> before that commit.
> > If your answer is "won't fix", state it explicitly please.
>
> Won't fix.
Can't be, for the same reason the bug 218353 was a regression and had to
be fixed.
prev parent reply other threads:[~2026-09-11 18:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 21:59 Alex Romosan
2026-09-08 22:22 ` Hanabishi
2026-09-09 0:25 ` David Sterba
2026-09-09 1:13 ` Qu Wenruo
2026-09-10 10:39 ` Thorsten Leemhuis
2026-09-11 18:21 ` David Sterba
2026-09-11 18:50 ` Alex Romosan
2026-09-11 23:42 ` Qu Wenruo
2026-09-09 14:18 ` Hanabishi
2026-09-09 21:58 ` Qu Wenruo
2026-09-09 23:35 ` Hanabishi
2026-09-10 0:02 ` Qu Wenruo
2026-09-11 18:11 ` 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=20260911181146.GD54722@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 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®