netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+1a55be5c9d955093937c@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, davem@davemloft.net,
	 edumazet@google.com, hpa@zytor.com, jhs@mojatatu.com,
	jiri@resnulli.us,  kuba@kernel.org, linux-kernel@vger.kernel.org,
	luto@kernel.org,  mingo@redhat.com, netdev@vger.kernel.org,
	pabeni@redhat.com,  praveen.kannoju@oracle.com,
	syzkaller-bugs@googlegroups.com,  tglx@linutronix.de,
	x86@kernel.org, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [kernel?] WARNING in emulate_vsyscall (2)
Date: Fri, 05 Jul 2024 09:53:02 -0700	[thread overview]
Message-ID: <00000000000084fd82061c82e523@google.com> (raw)
In-Reply-To: <0000000000005c2f9906153555b1@google.com>

syzbot suspects this issue was fixed by commit:

commit 33fb988b67050d9bb512f77f08453fa00088943c
Author: Praveen Kumar Kannoju <praveen.kannoju@oracle.com>
Date:   Wed May 8 13:36:17 2024 +0000

    net/sched: adjust device watchdog timer to detect stopped queue at right time

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1163e569980000
start commit:   480e035fc4c7 Merge tag 'drm-next-2024-03-13' of https://gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e5b814e91787669
dashboard link: https://syzkaller.appspot.com/bug?extid=1a55be5c9d955093937c
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11a64776180000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=142939b1180000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net/sched: adjust device watchdog timer to detect stopped queue at right time

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

           reply	other threads:[~2024-07-05 16:53 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <0000000000005c2f9906153555b1@google.com>]

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=00000000000084fd82061c82e523@google.com \
    --to=syzbot+1a55be5c9d955093937c@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hpa@zytor.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=praveen.kannoju@oracle.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).