linux-kernel - Re: Build regressions/improvements in v3.0-rc5

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

Message-Id: <201107021038.33066.arnd@arndb.de>
Date:	Sat, 2 Jul 2011 10:38:32 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org
Subject: Re: Build regressions/improvements in v3.0-rc5

On Saturday 02 July 2011 01:15:16 Mike Frysinger wrote:
> 
> On Fri, Jul 1, 2011 at 18:05, Arnd Bergmann wrote:
> > --- a/kernel/resource.c
> > +++ b/kernel/resource.c
> > @@ -21,7 +21,7 @@
> >  #include <linux/pfn.h>
> >  #include <asm/io.h>
> >
> > -
> > +#ifdef IO_SPACE_LIMIT
> >  struct resource ioport_resource = {
> >        .name   = "PCI IO",
> >        .start  = 0,
> > @@ -29,6 +29,7 @@ struct resource ioport_resource = {
> >        .flags  = IORESOURCE_IO,
> >  };
> >  EXPORT_SYMBOL(ioport_resource);
> > +#endif
> 
> hmm, asm-generic/io.h unconditionally sets this to 0xffff.  should
> that depend on CONFIG_HAS_IOPORT ?

Yes, that's probably another small change we should do. Right now,
building without HAS_IOPORT is broken in little ways all over the
place, so I expect there will be more of these once we look in all
the places. Regarding asm-generic/io.h, we probably want to
conditionally disable large parts of it.

Thanks,

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