linux-kernel - Re: Build breakage due to latest ARM fixes

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:	Sat, 3 Aug 2013 01:41:11 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Olof Johansson <olof@...om.net>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Build breakage due to latest ARM fixes

On Fri, Aug 02, 2013 at 05:24:21PM -0700, Olof Johansson wrote:
> On Fri, Aug 2, 2013 at 5:07 PM, Russell King - ARM Linux
> <linux@....linux.org.uk> wrote:
> > On Fri, Aug 02, 2013 at 04:41:11PM -0700, Olof Johansson wrote:
> >> Russell,
> >>
> >> Looks like you sent up some fixes to Linus that broke one of the atmel
> >> configs (CONFIG_MMU=n):
> >>
> >> commit 48be69a026b2c1 ARM: move signal handlers into a vdso-like page
> >>
> >> seems to have caused it:
> >>
> >> arch/arm/kernel/signal.c: In function 'setup_return':
> >> arch/arm/kernel/signal.c:413:25: error: 'mm_context_t' has no member
> >> named 'sigpage'
> >>
> >> I see it with at91x40_defconfig.
> >
> > I'll look into that.  Obviously, I never build nommu because it isn't
> > part of the build system and the nommu platform I do have - OKI67001 -
> > doesn't have mainline kernel support.  (And if it did, it would not be
> > DT, so I doubt it's submittable.)
> 
> I just noticed a whole bunch of boot/runtime failures too across the board too.
> 
> tegra2 seaboard, exynos arndale, ux500 snowball all panicked. Panda,
> cubox and sama5 were the only systems that stayed up. Note that I
> don't do much with them per boot though, so with more runtime they
> might have hit something too.
> 
> Some of the oopses below, they're probably not very useful though. Let
> me know if I can help collect data in any way.

Gah, it looks like I didn't commit an update to these patches.

> Maybe it's better to move this feature work to -next and iron out the
> kinks there? :(

Tell me how I can put this stuff into -next _and_ keep it secret because
it's security related.  The two things are totally incompatible with each
other.  Sorry.
--
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/