netdev - Re: [PATCH net 0/1] af_iucv: Validate socket address length in iucv_sock

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] [day] [month] [year] [list]

Date:	Tue, 19 Jan 2016 14:23:57 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	ubraun@...ux.vnet.ibm.com
Cc:	mschwid2@...ux.vnet.ibm.com, heicars2@...ux.vnet.ibm.com,
	netdev@...r.kernel.org, linux-s390@...r.kernel.org,
	ubraunu@...ux.vnet.ibm.com
Subject: Re: [PATCH net 0/1] af_iucv: Validate socket address length in
 iucv_sock_bind() 

From: Ursula Braun <ubraun@...ux.vnet.ibm.com>
Date: Tue, 19 Jan 2016 10:41:32 +0100

> this patch fixes a problem reported by Dmitry Vyukov in december. It is built
> and intended for the next-tree.

A bug fix is not appropriate for the next tree.

All bug fixes should target 'net'.  You even contacted me privately
asking me to queue this up for -stable.  Submitting something for
net-next and wanting a -stable backport is doubly inappropriate.

Things don't go to -stable unless it's in Linus's tree.  'net' is
for bug fixes, 'net-next' (closed right now) is for new features,
cleanups, and fixes to code only present in 'net-next'.

Anyways I applied this to 'net' and queued it up for -stable.