All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+989efe781c74de1ddb54@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	phind.uet@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in packet_sendmsg
Date: Wed, 11 Aug 2021 22:19:10 -0700	[thread overview]
Message-ID: <000000000000f6e6b305c955dff5@google.com> (raw)
In-Reply-To: <20210812045047.2548-1-hdanton@sina.com>

Hello,

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

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



Tested on:

commit:         761c6d7e Merge tag 'arc-5.14-rc6' of git://git.kernel...
git tree:       upstream
dashboard link: https://syzkaller.appspot.com/bug?extid=989efe781c74de1ddb54
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=147a5779300000


WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+989efe781c74de1ddb54@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel-mentees@lists.linuxfoundation.org,
	 linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	phind.uet@gmail.com,  syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in packet_sendmsg
Date: Wed, 11 Aug 2021 22:19:10 -0700	[thread overview]
Message-ID: <000000000000f6e6b305c955dff5@google.com> (raw)
In-Reply-To: <20210812045047.2548-1-hdanton@sina.com>

Hello,

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

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



Tested on:

commit:         761c6d7e Merge tag 'arc-5.14-rc6' of git://git.kernel...
git tree:       upstream
dashboard link: https://syzkaller.appspot.com/bug?extid=989efe781c74de1ddb54
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=147a5779300000

_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2021-08-12  5:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 23:59 [PATCH] net: drop skbs in napi->rx_list when removing the napi context Nguyen Dinh Phi
2021-08-11 23:59 ` Nguyen Dinh Phi
2021-08-12  4:50 ` Hillf Danton
2021-08-12  5:19   ` syzbot [this message]
2021-08-12  5:19     ` [syzbot] memory leak in packet_sendmsg syzbot
2021-08-12  7:07 ` [PATCH] net: drop skbs in napi->rx_list when removing the napi context Eric Dumazet
2021-08-12  7:07   ` Eric Dumazet via Linux-kernel-mentees
2021-08-12 19:17   ` Phi Nguyen
2021-08-12 19:17     ` Phi Nguyen
2021-08-13 10:16     ` Eric Dumazet
2021-08-13 10:16       ` Eric Dumazet
2021-08-13 10:51       ` Nguyen Dinh Phi
2021-08-13 10:51         ` Nguyen Dinh Phi
  -- strict thread matches above, loose matches on Subject: below --
2021-07-30 21:08 [syzbot] memory leak in packet_sendmsg 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=000000000000f6e6b305c955dff5@google.com \
    --to=syzbot+989efe781c74de1ddb54@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=phind.uet@gmail.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.