From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
linux-btrfs@vger.kernel.org
Subject: Re: for-next: KCSAN failures on 6130a25681d4 (kdave/for-next) Merge branch 'for-next-next-v5.20-20220804' into for-next-20220804
Date: Mon, 5 Sep 2022 17:42:03 +0200 [thread overview]
Message-ID: <20220905154203.GJ13489@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H7XCZnsCfiz9yAgfSP8rekx7YntVKphdDu8LLSehJ1EAQ@mail.gmail.com>
On Tue, Aug 09, 2022 at 08:35:42AM +0100, Filipe Manana wrote:
> On Tue, Aug 9, 2022 at 4:33 AM Zygo Blaxell
> <ce3g8jdj@umail.furryterror.org> wrote:
> >
> > Some KCSAN complaints I found while testing for other things...
> >
> > Here's one related to extent refs:
>
> It's about the block reserves, nothing to do with extents refs.
>
> These get reported every now and then like here:
>
> https://lore.kernel.org/linux-btrfs/CAAwBoOJDjei5Hnem155N_cJwiEkVwJYvgN-tQrwWbZQGhFU=cA@mail.gmail.com/
>
> It's actually harmless, but if we keep it like this, we'll keep
> getting reports in the future.
Can we add some kind of annotation so KCSAN understands that? The ->full
member would be accessed using a helper when outside of the lock so the
annotation can be there.
next prev parent reply other threads:[~2022-09-05 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 3:31 for-next: KCSAN failures on 6130a25681d4 (kdave/for-next) Merge branch 'for-next-next-v5.20-20220804' into for-next-20220804 Zygo Blaxell
2022-08-09 7:35 ` Filipe Manana
2022-09-05 15:42 ` David Sterba [this message]
2022-09-05 15:50 ` David Sterba
2022-09-05 16:05 ` Filipe Manana
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=20220905154203.GJ13489@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=fdmanana@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox