All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+c94a3675a626f6333d74@syzkaller.appspotmail.com>,
	avihaih@nvidia.com, dledford@redhat.com, haakon.bugge@oracle.com,
	leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: corrupted list in rdma_listen (2)
Date: Mon, 6 Dec 2021 13:35:50 -0400	[thread overview]
Message-ID: <20211206173550.GQ5112@ziepe.ca> (raw)
In-Reply-To: <CACT4Y+bnJ5M84RjUONFYMXSOpzC5UOq2DxVNoQkq6c6nYwG9Og@mail.gmail.com>

On Mon, Dec 06, 2021 at 04:46:40PM +0100, Dmitry Vyukov wrote:
> On Mon, 6 Dec 2021 at 16:42, Jason Gunthorpe <jgg@ziepe.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

  reply	other threads:[~2021-12-06 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04  9:54 [syzbot] BUG: corrupted list in rdma_listen (2) syzbot
2021-12-06 15:41 ` Jason Gunthorpe
2021-12-06 15:46   ` Dmitry Vyukov
2021-12-06 17:35     ` Jason Gunthorpe [this message]
2021-12-07  8:37       ` Dmitry Vyukov
2021-12-07 17:15         ` Jason Gunthorpe
2022-02-08 16:46 ` 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=20211206173550.GQ5112@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=avihaih@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=dvyukov@google.com \
    --cc=haakon.bugge@oracle.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=syzbot+c94a3675a626f6333d74@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.