netdev - Re: [patch] xen-netback: double free on unload

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130624.014449.788391647881401988.davem@davemloft.net>
Date:	Mon, 24 Jun 2013 01:44:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	julia.lawall@...6.fr
Cc:	dan.carpenter@...cle.com, ian.campbell@...rix.com,
	xen-devel@...ts.xensource.com, netdev@...r.kernel.org,
	kernel-janitors@...r.kernel.org
Subject: Re: [patch] xen-netback: double free on unload

From: Julia Lawall <julia.lawall@...6.fr>
Date: Mon, 24 Jun 2013 08:31:31 +0100 (BST)

> On Mon, 24 Jun 2013, David Miller wrote:
> 
>> From: Dan Carpenter <dan.carpenter@...cle.com>
>> Date: Fri, 21 Jun 2013 09:20:08 +0300
>>
>> > There is a typo here, "i" vs "j", so we would crash on module_exit().
>> >
>> > Signed-off-by: Dan Carpenter <dan.carpenter@...cle.com>
>>
>> Please always explicitly state the tree for which a patch is
>> applicable.
>>
>> Here I figured it out by trial an error, trying to apply it
>> to 'net' (where it failed) and then 'net-next' (where it
>> applied cleanly).
>>
>> I should never have to play patch monkey games like that, you
>> need to tell me where a patch is targetted.
> 
> Shouldn't one always, by default, work on linux-next?

Bug fixes, especially serious ones, should be targetted at 'net'.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html