[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+atv60UELnQJqejS_Z+uBYYERha4-o1dViwVuSLpb-Tfw@mail.gmail.com>
Date: Tue, 7 Dec 2021 09:37:30 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: syzbot <syzbot+c94a3675a626f6333d74@...kaller.appspotmail.com>,
avihaih@...dia.com, dledford@...hat.com, haakon.bugge@...cle.com,
leon@...nel.org, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] BUG: corrupted list in rdma_listen (2)
On Mon, 6 Dec 2021 at 18:35, Jason Gunthorpe <jgg@...pe.ca> wrote:
>
> On Mon, Dec 06, 2021 at 04:46:40PM +0100, Dmitry Vyukov wrote:
> > On Mon, 6 Dec 2021 at 16:42, Jason Gunthorpe <jgg@...pe.ca> wrote:
> > >
> > > On Sat, Dec 04, 2021 at 01:54:17AM -0800, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot found the following issue on:
> > > >
> > > > HEAD commit: bf152b0b41dc Merge tag 'for_linus' of git://git.kernel.org..
> > >
> > > ??
> > >
> > > This commit is nearly a year old?
> > >
> > > $ git describe --contains bf152b0b41dc
> > > v5.12-rc4~28
> > >
> > > I think this has probably been fixed since, why did a report for such
> > > an old kernel get sent?
> >
> > Hi Jason,
> >
> > Oh, that's because the arm32 kernel was broken for that period, so
> > syzbot tested the latest working kernel. There is a more fresh x86_64
> > crash available on the dashboard:
> > https://syzkaller.appspot.com/bug?extid=c94a3675a626f6333d74
>
> ??
>
> There is nothing there newer than a year?
>
> Jason
In the Crashes table there are 2 crashes, one is the one that was
reported in this email and the second happened on upstream commit
5833291ab6de (you can search by this hash on the page).
5833291ab6de is newer than a year:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?id=5833291ab6de
Powered by blists - more mailing lists