Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751808AbbBURNV (ORCPT ); Sat, 21 Feb 2015 12:13:21 -0500 Received: from www62.your-server.de ([213.133.104.62]:40599 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751604AbbBURNT (ORCPT ); Sat, 21 Feb 2015 12:13:19 -0500 Message-ID: <54E8BCA9.4080603@iogearbox.net> Date: Sat, 21 Feb 2015 18:13:13 +0100 From: Daniel Borkmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Shachar Raindel , Thomas Graf CC: "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: Use-after-free oops in next-20150204 - probably nelink related References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1074 Lines: 29 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/