All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cca39e6e84a367a7e6f6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, michal.switala@infogain.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] general protection fault in dev_map_enqueue (2)
Date: Mon, 08 Jul 2024 09:49:02 -0700	[thread overview]
Message-ID: <000000000000b95d41061cbf302a@google.com> (raw)
In-Reply-To: <20240708160329.1868842-1-michal.switala@infogain.com>

Hello,

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

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

Tested on:

commit:         83c36e7c docs: networking: devlink: capitalise length ..
git tree:       bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=16870566980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=dcd1b5bf2c3bc3ac
dashboard link: https://syzkaller.appspot.com/bug?extid=cca39e6e84a367a7e6f6
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16d5d87e980000

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

       reply	other threads:[~2024-07-08 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240708160329.1868842-1-michal.switala@infogain.com>
2024-07-08 16:49 ` syzbot [this message]
2024-05-27  0:44 [syzbot] [bpf?] [net?] general protection fault in dev_map_enqueue (2) syzbot
2024-06-09 11:34 ` syzbot
2024-08-31 20:55 ` syzbot
2024-09-02  8:02   ` Sebastian Andrzej Siewior
2024-09-20 11:18     ` Toke Høiland-Jørgensen

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=000000000000b95d41061cbf302a@google.com \
    --to=syzbot+cca39e6e84a367a7e6f6@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.switala@infogain.com \
    --cc=syzkaller-bugs@googlegroups.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.