From: Petr Machata <petrm@mellanox.com>
To: syzbot <syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com>
Cc: amitc@mellanox.com, andy.shevchenko@gmail.com,
bgolaszewski@baylibre.com, bp@alien8.de, davem@davemloft.net,
douly.fnst@cn.fujitsu.com, hpa@zytor.com, idosch@mellanox.com,
jon.maloy@ericsson.com, konrad.wilk@oracle.com,
len.brown@intel.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, puwen@hygon.cn,
rppt@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tipc-discussion@lists.sourceforge.net,
x86@kernel.org, ying.xue@windriver.com
Subject: Re: general protection fault in __bfs (2)
Date: Fri, 19 Jun 2020 14:17:51 +0200 [thread overview]
Message-ID: <87wo43jllc.fsf@mellanox.com> (raw)
In-Reply-To: <000000000000320bcb05a863a04c@google.com>
syzbot <syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com> writes:
> syzbot suspects this bug was fixed by commit:
>
> commit 46ca11177ed593f39d534f8d2c74ec5344e90c11
> Author: Amit Cohen <amitc@mellanox.com>
> Date: Thu May 21 12:11:45 2020 +0000
>
> selftests: mlxsw: qos_mc_aware: Specify arping timeout as an integer
That does not sound right. The referenced commit is a shell script fix.
prev parent reply other threads:[~2020-06-19 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 18:23 general protection fault in __bfs (2) syzbot
2019-02-07 3:42 ` syzbot
2019-03-11 13:27 ` syzbot
2019-03-11 13:49 ` Andy Shevchenko
2019-03-11 13:49 ` Andy Shevchenko
2019-03-28 16:47 ` Linus Walleij
2019-03-28 16:47 ` Linus Walleij
2020-06-18 22:52 ` syzbot
2020-06-19 12:17 ` Petr Machata [this message]
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=87wo43jllc.fsf@mellanox.com \
--to=petrm@mellanox.com \
--cc=amitc@mellanox.com \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=idosch@mellanox.com \
--cc=jon.maloy@ericsson.com \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzbot+c58fa3b1231d2ea0c4d3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=x86@kernel.org \
--cc=ying.xue@windriver.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.