linux-kernel - Re: [PATCH v2 06/13] backports: update dependencies map file

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:	Wed, 5 Nov 2014 21:13:26 +0100
From:	"Luis R. Rodriguez" <mcgrof@...e.com>
To:	Johannes Berg <johannes@...solutions.net>
Cc:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	backports@...r.kernel.org, linux-kernel@...r.kernel.org,
	yann.morin.1998@...e.fr, mmarek@...e.cz, sassmann@...nic.de
Subject: Re: [PATCH v2 06/13] backports: update dependencies map file

On Wed, Nov 05, 2014 at 08:54:11AM +0100, Johannes Berg wrote:
> On Tue, 2014-11-04 at 19:18 -0800, Luis R. Rodriguez wrote:
> > From: "Luis R. Rodriguez" <mcgrof@...e.com>
> > 
> > During development of kernel integration support using CONFIG_BACKPORT
> > was evaluated as a prefix over CPTCFG even for packaging backports,
> > for some reason this change lifted some restrictions one some device
> > drivers which was present before and as such requires some changes to
> > the dependencies map file to ensure correct compilation for respective
> > kernel versions.
> 
> This is confusing ... I think what you're trying to say is that you
> noticed it because your integration system was broken and not honouring
> restrictions properly?

No I verified each reported case I got and verified the issues found
were valid. For some reason some of these drivers were not allowed to
compile on some older versions, and from what me and Hauke could tell
they should, but they weren't. So the new annotations on requirements
are valid.

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