From: syzbot <syzbot+6eb09d75211863f15e3e@syzkaller.appspotmail.com>
To: phind.uet@gmail.com
Cc: phind.uet@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nfc?] memory leak in skb_copy (2)(test updated patch)
Date: Mon, 20 Nov 2023 23:14:38 -0800 [thread overview]
Message-ID: <000000000000043a22060aa45b5e@google.com> (raw)
In-Reply-To: <be80be80-eb37-bea1-43c8-0c97b133f676@gmail.com>
>
> #syz
unknown command "test:git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git"
> test:git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
parent reply other threads:[~2023-11-21 7:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <be80be80-eb37-bea1-43c8-0c97b133f676@gmail.com>]
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=000000000000043a22060aa45b5e@google.com \
--to=syzbot+6eb09d75211863f15e3e@syzkaller.appspotmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox