public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: syzbot <syzbot+af9492708df9797198d6@syzkaller•appspotmail.com>
To: andrii@kernel•org, ast@kernel•org, bpf@vger•kernel.org,
	 daniel@iogearbox•net, davem@davemloft•net, eadavis@qq•com,
	eddyz87@gmail•com,  haoluo@google•com, hawk@kernel•org,
	john.fastabend@gmail•com,  jolsa@kernel•org, kpsingh@kernel•org,
	kuba@kernel•org,  linux-kernel@vger•kernel.org,
	martin.lau@linux•dev, netdev@vger•kernel.org,  sdf@google•com,
	song@kernel•org, syzkaller-bugs@googlegroups•com,
	 toke@kernel•org, yonghong.song@linux•dev
Subject: Re: [syzbot] [bpf?] [net?] general protection fault in dev_map_enqueue
Date: Wed, 17 Apr 2024 07:49:03 -0700	[thread overview]
Message-ID: <000000000000a693f106164bf4c7@google.com> (raw)
In-Reply-To: <87il0huixn.fsf@toke.dk>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+af9492708df9797198d6@syzkaller•appspotmail.com

Tested on:

commit:         443574b0 riscv, bpf: Fix kfunc parameters incompatibil..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
console output: https://syzkaller.appspot.com/x/log.txt?x=125ea0e3180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=af9492708df9797198d6
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=156227cd180000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-04-17 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 19:00 [syzbot] [bpf?] [net?] general protection fault in dev_map_enqueue syzbot
2024-03-27  8:10 ` syzbot
2024-03-27 15:19   ` Alexei Starovoitov
2024-03-28  8:58     ` Jesper Dangaard Brouer
2024-03-28 20:39       ` Toke Høiland-Jørgensen
2024-03-31  9:08   ` [PATCH] bpf: fix null ptr deref " Edward Adam Davis
2024-04-01 11:00     ` Jesper Dangaard Brouer
2024-04-02  3:03       ` Edward Adam Davis
2024-04-04 11:03         ` Jesper Dangaard Brouer
2024-04-04 21:02       ` Toke Høiland-Jørgensen
2024-04-05  3:55         ` [syzbot] [bpf?] [net?] general protection fault " syzbot
2024-04-08 15:30           ` Toke Høiland-Jørgensen
2024-04-08 22:03             ` syzbot
2024-04-16 20:55               ` Toke Høiland-Jørgensen
2024-04-17 14:49                 ` syzbot [this message]
2024-04-17 19:18                   ` Toke Høiland-Jørgensen
2024-04-18  2:51                     ` 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=000000000000a693f106164bf4c7@google.com \
    --to=syzbot+af9492708df9797198d6@syzkaller$(echo .)appspotmail.com \
    --cc=andrii@kernel$(echo .)org \
    --cc=ast@kernel$(echo .)org \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=eadavis@qq$(echo .)com \
    --cc=eddyz87@gmail$(echo .)com \
    --cc=haoluo@google$(echo .)com \
    --cc=hawk@kernel$(echo .)org \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=jolsa@kernel$(echo .)org \
    --cc=kpsingh@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=martin.lau@linux$(echo .)dev \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sdf@google$(echo .)com \
    --cc=song@kernel$(echo .)org \
    --cc=syzkaller-bugs@googlegroups$(echo .)com \
    --cc=toke@kernel$(echo .)org \
    --cc=yonghong.song@linux$(echo .)dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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