From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: syzbot <syzbot+858534c396b0cdd291d2@syzkaller.appspotmail.com>,
"clm@fb.com" <clm@fb.com>, "dsterba@suse.com" <dsterba@suse.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"osandov@fb.com" <osandov@fb.com>,
"sweettea-kernel@dorminy.me" <sweettea-kernel@dorminy.me>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] WARNING in cow_file_range_inline
Date: Wed, 26 Oct 2022 10:14:26 +0200 [thread overview]
Message-ID: <20221026081426.GP5824@twin.jikos.cz> (raw)
In-Reply-To: <b9fb66a0-5516-d1d4-34d6-da91c60c56cf@wdc.com>
On Wed, Oct 26, 2022 at 07:30:02AM +0000, Johannes Thumshirn wrote:
> On 26.10.22 00:19, syzbot wrote:
> Not sure how applicable this is. The reproducer configures failslab to
> fail every 16th call and then complains about -ENOMEM ¯\_(ツ)_/¯
This still has some value I think, though we can't do much when an
ENOMEM is hit, at least from this report I see the way it's reported
back to user can be improved.
For EIO and EUCLEAN we don't dump the full stack trace because such
errors can happen during testing a lot, we may add ENOMEM as well. The
stack is supposed to be noisy for errors we want to know about, eg.
ENOSPC during transaction commit that would point to a bug in the
reservations.
next prev parent reply other threads:[~2022-10-26 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 22:18 syzbot
2022-10-26 7:30 ` Johannes Thumshirn
2022-10-26 8:14 ` David Sterba [this message]
2023-01-21 0:36 ` syzbot
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=20221026081426.GP5824@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Johannes.Thumshirn@wdc.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=sweettea-kernel@dorminy.me \
--cc=syzbot+858534c396b0cdd291d2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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®