linux-kernel - Re: [GIT PULL] parisc fixes for kernel v4.19

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181002211645.GA6454@kroah.com>
Date:   Tue, 2 Oct 2018 14:16:45 -0700
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Helge Deller <deller@....de>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        John David Anglin <dave.anglin@...l.net>
Subject: Re: [GIT PULL] parisc fixes for kernel v4.19

On Tue, Oct 02, 2018 at 11:02:13PM +0200, Helge Deller wrote:
> Hi Greg,
> 
> please pull a last set of fixes for the parisc architecture for kernel 4.19 from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.19-3
> 
> The major change is for parisc64 to use a 64-bit suseconds_t type to
> match what glibc expects for 64-bit userspace. It's an ABI change, but
> since we don't have a 64-bit userspace on parisc yet, it won't introduce
> a breakage.

Isn't it a bit "late" in the release cycle for such a change?  Why not
do this on the -rc1 release?

> Other than that we simply drop unused code and outdated gcc version
> checks.

Why are those needed now?

thanks,

greg k-h