All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@mellanox.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+3b4acab09b6463472d0a@syzkaller.appspotmail.com>,
	danielj@mellanox.com, dledford@redhat.com,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Johannes Berg <johannes.berg@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rdma@vger.kernel.org, monis@mellanox.com,
	Paolo Abeni <pabeni@redhat.com>,
	parav@mellanox.com, roland@purestorage.com,
	syzkaller-bugs@googlegroups.com, yuval.shaia@oracle.com
Subject: Re: WARNING: ODEBUG bug in process_one_req
Date: Thu, 22 Mar 2018 15:20:31 +0200	[thread overview]
Message-ID: <20180322132031.GC19440@mtr-leonro.local> (raw)
In-Reply-To: <CACT4Y+Ya8iMgV=7YGgsO2XnusF9tnGcHHPF5U5oNjQz_eJ+vMw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

On Thu, Mar 22, 2018 at 02:10:21PM +0100, Dmitry Vyukov wrote:
> This bug is actively happening several times per day, if such bug is
> closed syzbot will open another bug on the next crash.
> This bug has a reproducer, why do you think it is invalid?

I tried to reproduce it on latest rdma-next and failed, so wanted to
start from clean page and see if it is still relevant.

Does it still reproduce on latest rdma-next?

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-03-22 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 20:59 WARNING: ODEBUG bug in process_one_req syzbot
2018-03-22 12:48 ` Leon Romanovsky
2018-03-22 13:10   ` Dmitry Vyukov
2018-03-22 13:20     ` Leon Romanovsky [this message]
2018-03-22 13:36       ` Dmitry Vyukov
2018-03-22 14:29         ` Leon Romanovsky
2018-03-22 14:47           ` Dmitry Vyukov
2018-03-22 15:13             ` Leon Romanovsky
2018-03-22 15:31               ` Leon Romanovsky

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=20180322132031.GC19440@mtr-leonro.local \
    --to=leonro@mellanox.com \
    --cc=danielj@mellanox.com \
    --cc=dledford@redhat.com \
    --cc=dvyukov@google.com \
    --cc=jgg@ziepe.ca \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=monis@mellanox.com \
    --cc=pabeni@redhat.com \
    --cc=parav@mellanox.com \
    --cc=roland@purestorage.com \
    --cc=syzbot+3b4acab09b6463472d0a@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yuval.shaia@oracle.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.