linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
	Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Viktor Kuzmin <kvaster@gmail.com>
Subject: Re: Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2
Date: Thu, 20 Oct 2022 15:11:04 +0200	[thread overview]
Message-ID: <20221020131104.GF13389@suse.cz> (raw)
In-Reply-To: <13418d37-ebba-82d2-4e1b-4e48201342c7@leemhuis.info>

On Mon, Oct 17, 2022 at 02:00:30PM +0200, Thorsten Leemhuis wrote:
> On 14.10.22 13:07, David Sterba wrote:
> > On Tue, Oct 11, 2022 at 02:09:50PM +0200, Thorsten Leemhuis wrote:
> >> Hi, this is your Linux kernel regression tracker speaking.
> >>
> >> David, I noticed a regression report in bugzilla.kernel.org apparently
> >> caused by a changed of yours. As many (most?) kernel developer don't
> >> keep an eye on the bug-tracker, I decided to forward the report by mail.
> >> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216559 :
> > 
> > Thanks, you don't need to forward the mails as I'm on CC of all bugzilla
> > updates where the btrfs virtual assignee is also present.
> 
> Hmmm. Do you want to make my life easier or want to get less mail? I
> thought about this for a while. Unless you strongly object, I would like
> to continue forwarding them for the following reasons:
> 
> * you might be on vacation or AFK for other reasons; your Comaintainers
> that were CCed would know and likely then help out
> * CCing the list makes other people notice the issue and gives them a
> chance to help (Qu Wenruo replied in bugzilla shortly after I sent the
> mail you quoted, which might or might not be due to my mail).
> * regression tracking is hard already; it would make it a lot harder if
> I'm forced to make and maintain notes how each and every maintainer
> would like me to handle situations like this
> * right now I need to send one mail anyway to add a regression to the
> tracking

No problem with continuing the way it is, the reasons above make sense.

  reply	other threads:[~2022-10-20 13:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 12:09 Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2 Thorsten Leemhuis
2022-10-14 11:07 ` David Sterba
2022-10-17 12:00   ` Thorsten Leemhuis
2022-10-20 13:11     ` David Sterba [this message]
2022-11-04 12:12 ` Bug 216559 - btrfs crash root mount RAID0 caused by ac0677348f3c2 #forregzbot Thorsten Leemhuis

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=20221020131104.GF13389@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kvaster@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).