mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Shachar Raindel <raindel@mellanox.com>, Thomas Graf <tgraf@suug.ch>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Use-after-free oops in next-20150204 - probably nelink related
Date: Sat, 21 Feb 2015 18:13:13 +0100	[thread overview]
Message-ID: <54E8BCA9.4080603@iogearbox.net> (raw)
In-Reply-To: <AM3PR05MB0935A7C27C0F9D9BCD5B70E5DC2B0@AM3PR05MB0935.eurprd05.prod.outlook.com>

On 02/21/2015 04:36 PM, Shachar Raindel wrote:
...
>> This is most likely rhashtable related. The fixes for the
>> use-after-free issues have been merged Feb 6 so they are probably
>> not included in the Feb 04 snapshot that you use.
>>
>> The relevant net-next commits are:
>> commit 020219a69d40a205dad12b0ea1e6a46153793368
>> commit cf52d52f9ccb9966ac019d9f79824195583e3e6c
>> commit 2af4b52988fd4f7ae525fcada29d4db8680033d6
>> commit a5ec68e3b8f2c95ea1a5d23dd543abbe0c8d0624
>
> Most likely so - haven't seen this reproducing so far on next-20150219,
> which contains the relevant commits.

Thanks for double checking!

> BTW, why is there no MAINTAINERS entry for the netlink subsystem?

Well, if in doubt where to send a bug report, then :

   scripts/get_maintainer.pl -f net/netlink/

Make sure to Cc netdev in any case.

  reply	other threads:[~2015-02-21 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21 15:36 Shachar Raindel
2015-02-21 17:13 ` Daniel Borkmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-18 15:52 Shachar Raindel
2015-02-19 15:48 ` Thomas Graf

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=54E8BCA9.4080603@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=raindel@mellanox.com \
    --cc=tgraf@suug.ch \
    /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
all inboxes | Powered by JetHome®