linux-kernel - Re: [PATCH v4 00/12] allow BFLT executables on systems with a MMU

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:	Fri, 22 Jul 2016 20:22:51 +0100
From:	Russell King - ARM Linux <linux@...linux.org.uk>
To:	Greg Ungerer <gerg@...ux-m68k.org>
Cc:	Nicolas Pitre <nicolas.pitre@...aro.org>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	Alexander Viro <viro@...iv.linux.org.uk>,
	David Howells <dhowells@...hat.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v4 00/12] allow BFLT executables on systems with a MMU

On Fri, Jul 22, 2016 at 05:28:13PM +1000, Greg Ungerer wrote:
> On 22/07/16 00:48, Nicolas Pitre wrote:
> > On Thu, 21 Jul 2016, Greg Ungerer wrote:
> >> Hi Nicolas,
> >>
> >> On 21/07/16 05:22, Nicolas Pitre wrote:
> >>> This series provides the necessary changes to allow "flat" executable
> >>> binaries meant for no-MMU systems to actually run on systems with a MMU.
> >>> Also thrown in are various cleanups to binfmt_flat.c.
> >>
> >> I got to the bottom of why I couldn't run m68k flat binaries on
> >> an MMU enabled m68k system. I had to fix the regs setup, with the
> >> patch below. With this I can now run flat binaries on my ColdFire
> >> MMU enabled system.
> > 
> > Excellent!
> > 
> >> This change is completely independent of your patch series so I'll
> >> push this separately via the linux-m68k list and my m68knommu git
> >> tree.
> > 
> > OK.
> > 
> > Who should merge my patch series at this point?
> 
> If no-one else wants to carry it I can take it in the m68knommu
> git tree. But I would want to be sure everyone is good with it
> first.
> 
> Alan: are you happy with where this is at?
> rmk: ok with the arm flat.h change going via another tree?

I've no idea, sorry.  This is the first I've heard about this as I
haven't been copied with any of the patches, neither has the
linux-arm-kernel mailing list.

> (Link to v4 patches here https://lkml.org/lkml/2016/7/20/508 )

elinks tells me "Unable to retrieve https://lkml.org/lkml/2016/7/20/508:
SSL error" which is a common lkml.org error with elinks.  Also lkml.org
doesn't always work with firefox, especially if you try to follow threads
- I often end up with messages that are missing all content.  Even
openssl s_client gets refused by lkml.org:443 with a fatal SSL error.
(elinks gets "Handshake Failure", openssl gets "Internal Error".)

So, given that no one has seen this on the ARM side, I think there's
a need to post the patches so that it can be reviewed there, especially
so that the wider ARM audience can see what's going on, and ARM64 folk
can see as well.

In any case, I certainly won't be able to review it over this weekend.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.