netdev - Re: [PATCH] stable_kernel_rules.txt: Exclude networking from stable rules

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1379968445.3575.60.camel@joe-AO722>
Date:	Mon, 23 Sep 2013 13:34:05 -0700
From:	Joe Perches <joe@...ches.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	David Miller <davem@...emloft.net>, stephen@...workplumber.org,
	netdev@...r.kernel.org, Mikulas Patocka <mpatocka@...hat.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Rob Landley <rob@...dley.net>, linux-doc@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>, xfs@....sgi.com
Subject: Re: [PATCH] stable_kernel_rules.txt: Exclude networking from stable
 rules

On Sun, 2013-09-22 at 11:51 -0700, Christoph Hellwig wrote:
> This is also the preferred way to do it for XFS.  Maybe word it in a way
> that we can easily add subsystems.
> 
> To me it generally seems to be the best way to do it - having random Ccs
> and lots of stable trees doesn't seem like a very good way of handling
> it.

Maybe adding a mechanism to MAINTAINERS would be better.
Maybe a default B: (backport?) of stable@...r.kernel.org
with a per-subsystem override?

SUBSYSTEM TYPE
M:	maintainer@...il.address
L:	list@...il.address
S:	Supported
F:	file/pattern/
B:	stable@...il.address


--
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