linux-kernel - Re: [PATCH 0/3] rfkill_unregister() should always be followed by rfkill

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]

Date:	Mon, 14 Sep 2009 15:57:15 +0100
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Corentin Chary <corentincj@...aif.net>, linux-acpi@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Julia Lawall <julia@...u.dk>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: [PATCH 0/3] rfkill_unregister() should always be followed by
 rfkill_destroy()

Henrique de Moraes Holschuh wrote:
> On Mon, 14 Sep 2009, Corentin Chary wrote:
>   
>>  drivers/platform/x86/dell-laptop.c   |   36 ++++++++++++++++++++++-----------
>>  drivers/platform/x86/hp-wmi.c        |    2 +-
>>  drivers/platform/x86/thinkpad_acpi.c |    1 +
>>     
>
> These are also likely needed in 2.6.31, please add appropriate Cc: lines to
> stable@...nel.org while adding the Acked-By's.
>
>   

Do they meet the -stable criteria?

...
 - It must fix a real bug that bothers people (not a, "This could be a
   problem..." type thing).
 - It must fix a problem that causes a build error (but not for things
   marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
   security issue, or some "oh, that's not good" issue.  In short, something
   critical.
... (Documentation/stable_kernel_rules.txt)

Regards
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/