All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f363afac6b0ace576f45@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] WARNING in sock_map_destroy
Date: Sun, 29 Sep 2024 00:56:02 -0700	[thread overview]
Message-ID: <66f90812.050a0220.aab67.0012.GAE@google.com> (raw)
In-Reply-To: <74a699a0-d3b1-43c2-87a9-08e8336d9c6e@yandex.ru>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to apply patch:
checking file net/core/sock_map.c
patch: **** unexpected end of file in patch



Tested on:

commit:         3efc5736 Merge tag 'for-linus' of git://git.kernel.org..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=968c4fa762577d3f
dashboard link: https://syzkaller.appspot.com/bug?extid=f363afac6b0ace576f45
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=118ccd9f980000


       reply	other threads:[~2024-09-29  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <74a699a0-d3b1-43c2-87a9-08e8336d9c6e@yandex.ru>
2024-09-29  7:56 ` syzbot [this message]
     [not found] <20240929092855.205447-1-dmantipov@yandex.ru>
2024-09-29 10:55 ` [syzbot] [bpf?] [net?] WARNING in sock_map_destroy syzbot
     [not found] <20240929092816.205431-1-dmantipov@yandex.ru>
2024-09-29 10:31 ` syzbot
     [not found] <20240929092626.205369-1-dmantipov@yandex.ru>
2024-09-29 10:08 ` syzbot
     [not found] <54ba4ba9-46f2-4ee9-a199-ee2661ab018f@yandex.ru>
2024-09-29  7:57 ` syzbot
     [not found] <e01d6067-7afb-4583-a65f-ae9519d303ea@yandex.ru>
2024-09-29  7:56 ` syzbot
2024-08-27 10:46 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=66f90812.050a0220.aab67.0012.GAE@google.com \
    --to=syzbot+f363afac6b0ace576f45@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --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.