linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Sabrina Dubroca <sd@queasysnail.net>,
	Cong Wang <xiyou.wangcong@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	syzbot+41f9c04b50ef70c66947@syzkaller.appspotmail.com,
	christian.brauner@ubuntu.com, David Miller <davem@davemloft.net>,
	Florian Westphal <fw@strlen.de>, Jiri Benc <jbenc@redhat.com>,
	Kirill Tkhai <ktkhai@virtuozzo.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lucien xin <lucien.xin@gmail.com>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in rtnetlink_put_metrics
Date: Wed, 1 Aug 2018 10:28:54 +0200	[thread overview]
Message-ID: <18196855-1085-9c70-fc58-fdcbe4060d21@gmail.com> (raw)
In-Reply-To: <20180801081537.GA31982@bistromath.localdomain>

On 8/1/18 10:15 AM, Sabrina Dubroca wrote:
> ip -net peerA route add fec0:B::/64 via fec0:A:: mtu 1300

I am on vacation right now with limited access to internet, so not able
to take a look.

In submitting the fib6_info changes I did tests like this and did not
see memleak reports (and verified the metrics refcnts with printks), so
I am surprised to see your patch in this area. Will take a look when I
can but that will not be for a couple more weeks.

  reply	other threads:[~2018-08-01  8:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 12:31 KASAN: use-after-free Read in rtnetlink_put_metrics syzbot
2018-07-31 12:41 ` Eric Dumazet
2018-07-31 13:40   ` Sabrina Dubroca
2018-07-31 21:53     ` David Miller
2018-07-31 23:03     ` Cong Wang
2018-08-01  8:15       ` Sabrina Dubroca
2018-08-01  8:28         ` David Ahern [this message]
2018-08-02  5:23         ` Cong Wang
2018-08-01 18:46       ` David Miller
2018-08-01 19:26         ` Sabrina Dubroca

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=18196855-1085-9c70-fc58-fdcbe4060d21@gmail.com \
    --to=dsahern@gmail.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=fw@strlen.de \
    --cc=jbenc@redhat.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=syzbot+41f9c04b50ef70c66947@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).