From: Ido Schimmel <idosch@idosch.org>
To: David Ahern <dsahern@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
syzkaller@googlegroups.com, idosch@mellanox.com
Subject: Re: [PATCH net] rtnetlink: Refine sanity checks in rtnl_fdb_{add|del}
Date: Fri, 30 Nov 2018 18:02:08 +0200 [thread overview]
Message-ID: <20181130160208.GB22321@splinter.mtl.com> (raw)
In-Reply-To: <31f441a7-9bc8-b087-26ce-5e7c1910b388@gmail.com>
On Fri, Nov 30, 2018 at 08:59:09AM -0700, David Ahern wrote:
> This does not repro for me:
> # ./a.out
> Invalid address length 6 - must be 4 bytes
> RTNETLINK answers: No buffer space available
> RTNETLINK answers: Operation not supported
> Invalid address length 6 - must be 4 bytes
> Invalid address length 6 - must be 4 bytes
> Invalid address length 6 - must be 4 bytes
> Invalid address length 6 - must be 16 bytes
> Invalid address length 6 - must be 16 bytes
> Invalid address length 6 - must be 16 bytes
>
> config available>?
You need a kernel with kmsan. See:
https://github.com/google/kmsan
next prev parent reply other threads:[~2018-12-01 3:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 13:35 [PATCH net] rtnetlink: Refine sanity checks in rtnl_fdb_{add|del} Eric Dumazet
2018-11-30 14:58 ` Ido Schimmel
2018-11-30 15:14 ` Eric Dumazet
2018-11-30 15:59 ` David Ahern
2018-11-30 16:02 ` Ido Schimmel [this message]
2018-11-30 16:10 ` Dmitry Vyukov
2018-11-30 16:17 ` Eric Dumazet
2018-11-30 17:00 ` Ido Schimmel
2018-12-03 23:52 ` David Miller
2018-12-04 15:58 ` Eric Dumazet
2018-11-30 15:36 ` David Ahern
2018-11-30 15:40 ` Eric Dumazet
2018-11-30 15:46 ` Eric Dumazet
2018-11-30 15:51 ` Eric Dumazet
2018-11-30 16:00 ` Ido Schimmel
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=20181130160208.GB22321@splinter.mtl.com \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@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.