[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240612-hofiert-hymne-11f5a03b7e73@brauner>
Date: Wed, 12 Jun 2024 13:48:06 +0200
From: Christian Brauner <brauner@...nel.org>
To: Marius Fleischer <fleischermarius@...il.com>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller@...glegroups.com,
harrisonmichaelgreen@...il.com
Subject: Re: possible deadlock in freeze_super
On Mon, Jun 10, 2024 at 02:52:36PM -0700, Marius Fleischer wrote:
> Hi,
>
> We would like to report the following bug which has been found by our
> modified version of syzkaller.
>
> ======================================================
> description: possible deadlock in freeze_super
> affected file: fs/super.c
> kernel version: 5.15.159
> kernel commit: a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6
I'm sorry but this is really inconsistent information.
The kernel version points to 5.15.159. The commit referenced right after
is for v6.9 though and it goes on...
> freeze_go_sync+0x1d6/0x320 fs/gfs2/glops.c:584
That function doesn't exist on v6.9 and has been removed in
commit b77b4a4815a9 ("gfs2: Rework freeze / thaw logic") which fixes the
deadlock you supposedly detected. So, this must be from a kernel prior
to v6.5.
In general we will ignore bug reports from automated tools that are not
the official syzkaller instance because stuff like this is stealing time
spent actually writing code or fixing bugs.
Powered by blists - more mailing lists