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:	Tue, 29 Mar 2011 09:23:03 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>, Shyam_Iyer@...l.com,
	mjg59@...f.ucam.org, Narendra_K@...l.com, viro@...iv.linux.org.uk,
	sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, Matt_Domsch@...l.com,
	Charles_Rose@...l.com, Jordan_Hargrave@...l.com
Subject: Re: [PATCH] Fix build failure when CONFIG_NLS is set to 'm' by
 allmodconfig

On Tue, 29 Mar 2011 09:18:04 -0700
Randy Dunlap <randy.dunlap@...cle.com> wrote:

> On 03/28/11 18:55, OGAWA Hirofumi wrote:
> > Randy Dunlap <randy.dunlap@...cle.com> writes:
> > 
> >>> I don't get this.. you should not be getting CONFIG_NLS=m unless you
> >>> have stripped you config files really.. :-) Is it possible to get
> >>> your .config to hit this issue.
> >>
> >> I haven't stripped any config files -- but they are randconfig files.
> >> Two (2) config files that cause build failures are attached.
> > 
> > config PCI_IOAPIC
> > 	bool
> > 	depends on PCI
> > 	depends on ACPI
> > 	depends on HOTPLUG
> > 	default y
> > 
> > select NLS if (DMI || ACPI)
> 
> Ugh.  That looks seriously mucked up.
> Dell people, have you checked what it is linux-next for this pci-label stuff?
> 
> Jesse, I would drop the b0rked pieces and ask for a new patch.

Should be the same as what's in Linus master at this point...  But yes
I'm tempted to revert since it's been nothing but trouble so far.

Narendra, any chance you can get me a fix today?  If not I'll queue up
a revert and you can try again in the next cycle.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ