All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com>
To: andrew+netdev@lunn.ch, andrew@lunn.ch, davem@davemloft.net,
	 edumazet@google.com, jason@zx2c4.com, jasowang@redhat.com,
	jhs@mojatatu.com,  jiri@resnulli.us, kuba@kernel.org,
	linux-kernel@vger.kernel.org,  mail@country-targeted-traffic.com,
	netdev@vger.kernel.org, pabeni@redhat.com,
	 syzkaller-bugs@googlegroups.com, vinicius.gomes@intel.com,
	 willemdebruijn.kernel@gmail.com, wireguard@lists.zx2c4.com,
	 xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net] INFO: task hung in tun_chr_close (5)
Date: Sun, 05 Jan 2025 07:45:01 -0800	[thread overview]
Message-ID: <677aa8fd.050a0220.380ff0.0019.GAE@google.com> (raw)
In-Reply-To: <000000000000bd671b06222de427@google.com>

syzbot has bisected this issue 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

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11535418580000
start commit:   7ed2d9158877 qed: fix possible uninit pointer read in qed_..
git tree:       net
final oops:     https://syzkaller.appspot.com/x/report.txt?x=13535418580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15535418580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fee25f93665c89ac
dashboard link: https://syzkaller.appspot.com/bug?extid=b0ae8f1abf7d891e0426
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=112374f8580000

Reported-by: syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2025-01-05 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-15 19:59 [syzbot] [wireguard?] INFO: task hung in tun_chr_close (5) syzbot
2024-11-19  1:31 ` [syzbot] [net] " syzbot
2025-01-05 15:45 ` syzbot [this message]
2026-03-31 17:17 ` 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=677aa8fd.050a0220.380ff0.0019.GAE@google.com \
    --to=syzbot+b0ae8f1abf7d891e0426@syzkaller.appspotmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jason@zx2c4.com \
    --cc=jasowang@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@country-targeted-traffic.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vinicius.gomes@intel.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=wireguard@lists.zx2c4.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 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.