[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACj3i70Dw5=B-k5hKEXpHg5DOhG2Hi-Xb4ZVpZWL+EYdX=jCeQ@mail.gmail.com>
Date: Wed, 2 May 2018 11:54:24 +0200
From: Jan Tulak <jtulak@...hat.com>
To: Eric Sandeen <sandeen@...deen.net>
Cc: Dmitry Vyukov <dvyukov@...gle.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Dave Chinner <david@...morbit.com>,
syzbot <syzbot+84a67953651a971809ba@...kaller.appspotmail.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-xfs <linux-xfs@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
"Theodore Ts'o" <tytso@....edu>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: WARNING: bad unlock balance in xfs_iunlock
On Mon, Apr 30, 2018 at 5:14 PM, Eric Sandeen <sandeen@...deen.net> wrote:
> On 4/30/18 9:02 AM, Dmitry Vyukov wrote:
>> Suggestions are welcome. Currently it says "syzbot hit the following
>> crash on upstream commit SHA1", which was supposed to mean just the
>> state of the source tree when the crash happened. But I am not a
>> native speaker, so perhaps I am saying not what I intend to say.
>>
>> There are also suggestions on report format improvement from +Ted
>> currently in works:
>> https://github.com/google/syzkaller/issues/565#issuecomment-380792942
>> Not sure if they make this distinction 100% clear, though.
>
> Maybe I was the only one who misunderstood, but something like
>
snip
You are not the only one, I (mis)understand it the same as you.
Jan
Powered by blists - more mailing lists