linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: syzbot <syzbot+222aa26d0a5dbc2e84fe@syzkaller.appspotmail.com>,
	syzkaller-bugs@googlegroups.com
Cc: amir73il@gmail.com, bpf@vger.kernel.org, daniel@iogearbox.net,
	davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
	jack@suse.cz, kuba@kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, penguin-kernel@i-love.sakura.ne.jp,
	peterz@infradead.org, torvalds@linux-foundation.org,
	willemdebruijn.kernel@gmail.com
Subject: Re: [syzbot] [fs?] INFO: task hung in synchronize_rcu (4)
Date: Sat, 20 May 2023 19:26:22 -0700	[thread overview]
Message-ID: <048219d7-2403-b898-129f-a0f85512cdf5@linux.dev> (raw)
In-Reply-To: <000000000000baea9905fc275a49@google.com>

On 5/20/23 3:13 PM, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    dcbe4ea1985d Merge branch '1GbE' of git://git.kernel.org/p..
> git tree:       net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=123ebd91280000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=f20b05fe035db814
> dashboard link: https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
> compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1495596a280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1529326a280000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/41b9dda0e686/disk-dcbe4ea1.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/64d9bece8f89/vmlinux-dcbe4ea1.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/42429896dca0/bzImage-dcbe4ea1.xz
> 
> The issue was bisected to:
> 
> commit 3b5d4ddf8fe1f60082513f94bae586ac80188a03
> Author: Martin KaFai Lau <kafai@fb.com>
> Date:   Wed Mar 9 09:04:50 2022 +0000
> 
>      bpf: net: Remove TC_AT_INGRESS_OFFSET and SKB_MONO_DELIVERY_TIME_OFFSET macro

I am afraid this bisect is incorrect. The commit removed a redundant macro and 
is a no-op change.



  reply	other threads:[~2023-05-21  2:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  2:01 [syzbot] [fs?] INFO: task hung in synchronize_rcu (4) syzbot
2023-05-20 22:13 ` syzbot
2023-05-21  2:26   ` Martin KaFai Lau [this message]
2023-05-21  5:04     ` Tetsuo Handa

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=048219d7-2403-b898-129f-a0f85512cdf5@linux.dev \
    --to=martin.lau@linux.dev \
    --cc=amir73il@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hdanton@sina.com \
    --cc=jack@suse.cz \
    --cc=kuba@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=syzbot+222aa26d0a5dbc2e84fe@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willemdebruijn.kernel@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).