From: Thomas Graf <tgraf@suug.ch>
To: Shachar Raindel <raindel@mellanox.com>
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: Thu, 19 Feb 2015 15:48:49 +0000 [thread overview]
Message-ID: <20150219154849.GA20562@casper.infradead.org> (raw)
In-Reply-To: <AM3PR05MB093578F143B8C4C1BC18D5F6DC2C0@AM3PR05MB0935.eurprd05.prod.outlook.com>
On 02/18/15 at 03:52pm, Shachar Raindel wrote:
> Hi,
>
> I'm running trinity inside a VM running linux-next tagged next-20150204.
>
> The kernel debugging infrastructure detected a use-after-free situation, probably in netlink:
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
next prev parent reply other threads:[~2015-02-19 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 15:52 Shachar Raindel
2015-02-19 15:48 ` Thomas Graf [this message]
2015-02-21 15:36 Shachar Raindel
2015-02-21 17:13 ` Daniel Borkmann
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=20150219154849.GA20562@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raindel@mellanox.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
all inboxes | Powered by JetHome®