netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+3b3296d032353c33184b@syzkaller.appspotmail.com>
To: a.p.zijlstra@chello.nl, acme@redhat.com, andi@firstfloor.org,
	davem@davemloft.net, dhowells@redhat.com, dsahern@gmail.com,
	jakub.kicinski@netronome.com, jeliantsurux@gmail.com,
	johannes.berg@intel.com, jolsa@kernel.org,
	linux-kernel@vger.kernel.org, namhyung@kernel.org,
	netdev@vger.kernel.org, nicolas.dichtel@6wind.com,
	syzkaller-bugs@googlegroups.com, tyhicks@canonical.com,
	willy@infradead.org
Subject: Re: memory leak in copy_net_ns
Date: Fri, 18 Oct 2019 21:00:01 -0700	[thread overview]
Message-ID: <0000000000001b4f0b05953b7c13@google.com> (raw)
In-Reply-To: <CAKK_rcj55g8WPCLrrLdT+8zWLXXOMVf0jhMyYQj9jndy_+i8qw@mail.gmail.com>

Hello,

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

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

Tested on:

commit:         43b815c6 Merge tag 'armsoc-fixes' of git://git.kernel.org/..
git tree:       https://github.com/google/kasan.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=d9ba1b8c7fca2c71
dashboard link: https://syzkaller.appspot.com/bug?extid=3b3296d032353c33184b
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
patch:          https://syzkaller.appspot.com/x/patch.diff?x=118f59e8e00000

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

      reply	other threads:[~2019-10-19  4:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 21:29 memory leak in copy_net_ns syzbot
2019-10-19  3:43 ` Takeshi Misawa
2019-10-19  4:00   ` syzbot [this message]

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=0000000000001b4f0b05953b7c13@google.com \
    --to=syzbot+3b3296d032353c33184b@syzkaller.appspotmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jeliantsurux@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tyhicks@canonical.com \
    --cc=willy@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).