From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: lkp <oliver.sang@intel.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, linux-btrfs@vger.kernel.org
Subject: Re: [btrfs] [confidence: ] c2e3930529: WARNING:at_fs/btrfs/block-group.c:#btrfs_put_block_group[btrfs]
Date: Fri, 14 Jan 2022 17:28:17 +0100 [thread overview]
Message-ID: <20220114162817.GC14046@twin.jikos.cz> (raw)
In-Reply-To: <YeFVtonXVkSJsdhq@debian9.Home>
On Fri, Jan 14, 2022 at 10:51:34AM +0000, Filipe Manana wrote:
> On Fri, Jan 14, 2022 at 04:23:31PM +0800, kernel test robot wrote:
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@intel.com>
>
> Known issue, and is fixed by:
>
> https://patchwork.kernel.org/project/linux-btrfs/patch/3aae7c6728257c7ce2279d6660ee2797e5e34bbd.1641300250.git.fdmanana@suse.com/
>
> But it's not yet on Linus' tree.
Will go as a post-rc1 fix at the latest.
WARNING: multiple messages have this Message-ID (diff)
From: David Sterba <dsterba@suse.cz>
To: lkp@lists.01.org
Subject: Re: [btrfs] [confidence: ] c2e3930529: WARNING:at_fs/btrfs/block-group.c:#btrfs_put_block_group[btrfs]
Date: Fri, 14 Jan 2022 17:28:17 +0100 [thread overview]
Message-ID: <20220114162817.GC14046@twin.jikos.cz> (raw)
In-Reply-To: <YeFVtonXVkSJsdhq@debian9.Home>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Fri, Jan 14, 2022 at 10:51:34AM +0000, Filipe Manana wrote:
> On Fri, Jan 14, 2022 at 04:23:31PM +0800, kernel test robot wrote:
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@intel.com>
>
> Known issue, and is fixed by:
>
> https://patchwork.kernel.org/project/linux-btrfs/patch/3aae7c6728257c7ce2279d6660ee2797e5e34bbd.1641300250.git.fdmanana(a)suse.com/
>
> But it's not yet on Linus' tree.
Will go as a post-rc1 fix at the latest.
next prev parent reply other threads:[~2022-01-14 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 8:23 [btrfs] [confidence: ] c2e3930529: WARNING:at_fs/btrfs/block-group.c:#btrfs_put_block_group[btrfs] kernel test robot
2022-01-14 8:23 ` kernel test robot
2022-01-14 10:51 ` Filipe Manana
2022-01-14 10:51 ` Filipe Manana
2022-01-14 16:28 ` David Sterba [this message]
2022-01-14 16:28 ` David Sterba
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=20220114162817.GC14046@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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.