[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221026081426.GP5824@twin.jikos.cz>
Date: Wed, 26 Oct 2022 10:14:26 +0200
From: David Sterba <dsterba@...e.cz>
To: Johannes Thumshirn <Johannes.Thumshirn@....com>
Cc: syzbot <syzbot+858534c396b0cdd291d2@...kaller.appspotmail.com>,
"clm@...com" <clm@...com>, "dsterba@...e.com" <dsterba@...e.com>,
"josef@...icpanda.com" <josef@...icpanda.com>,
"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"osandov@...com" <osandov@...com>,
"sweettea-kernel@...miny.me" <sweettea-kernel@...miny.me>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] WARNING in cow_file_range_inline
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.
Powered by blists - more mailing lists