From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+aa7d098bd6fa788fae8e@syzkaller.appspotmail.com>
Cc: "David Miller" <davem@davemloft.net>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Jiří Pírko" <jiri@resnulli.us>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>
Subject: Re: INFO: rcu detected stall in corrupted (4)
Date: Fri, 05 Mar 2021 14:27:55 -0800 [thread overview]
Message-ID: <87ft19nslw.fsf@vcostago-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <CACT4Y+Z1MD2VyjDbz5h7UhPqihSBCnOUjA0E5_DoJqAZEHciAg@mail.gmail.com>
Dmitry Vyukov <dvyukov@google.com> writes:
> On Fri, Sep 4, 2020 at 8:49 PM syzbot
> <syzbot+aa7d098bd6fa788fae8e@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 0f091e43 netlabel: remove unused param from audit_log_form..
>> git tree: net-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=14551a71900000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=61025c6fd3261bb1
>> dashboard link: https://syzkaller.appspot.com/bug?extid=aa7d098bd6fa788fae8e
>> compiler: gcc (GCC) 10.1.0-syz 20200507
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14eeda25900000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161472f5900000
>>
>> The issue was bisected to:
>>
>> commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22
>> Author: Vinicius Costa Gomes <vinicius.gomes@intel.com>
>> Date: Sat Sep 29 00:59:43 2018 +0000
>>
>> tc: Add support for configuring the taprio scheduler
>
> This still happens. The bisection and repro look correct, the repro
> also sets up taprio scheduler;
> https://syzkaller.appspot.com/bug?id=7349616606afa3c986c377792f7ccbf9daae1142
>
> Vinicius, could you please take a look? Thanks
Ugh.
Sure. Taking a look.
Cheers,
--
Vinicius
next prev parent reply other threads:[~2021-03-05 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 18:49 syzbot
2021-03-05 7:58 ` Dmitry Vyukov
2021-03-05 22:27 ` Vinicius Costa Gomes [this message]
[not found] <77217e8a-0b61-495c-963e-4c4e783fb202@gmail.com>
2026-05-22 14:28 ` syzbot
[not found] <7115ef32-e59e-4da4-978d-5488a20a0f7b@gmail.com>
2026-05-22 14:32 ` 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=87ft19nslw.fsf@vcostago-mobl2.amr.corp.intel.com \
--to=vinicius.gomes@intel.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+aa7d098bd6fa788fae8e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®