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:   Thu, 14 May 2020 08:26:24 +0100
From:   Will Deacon <will@...nel.org>
To:     David Miller <davem@...emloft.net>
Cc:     linux-kernel@...r.kernel.org, peterz@...radead.org,
        ndesaulniers@...gle.com, matt@...eblueprint.co.uk,
        sparclinux@...r.kernel.org, kernel-team@...roid.com,
        tglx@...utronix.de
Subject: Re: [RESEND PATCH 0/4] Rework sparc32 page-table layout

Hi David,

On Wed, May 13, 2020 at 03:32:26PM -0700, David Miller wrote:
> From: Will Deacon <will@...nel.org>
> Date: Tue, 14 Apr 2020 22:40:07 +0100
> 
> > This is a reposting of the patch series I sent previously to rework the
> > sparc32 page-table layout so that 'pmd_t' can be used safely with
> > READ_ONCE():
> > 
> > https://lore.kernel.org/lkml/20200324104005.11279-1-will@kernel.org
> > 
> > This is blocking the READ_ONCE() rework, which in turn allows us to
> > bump the minimum GCC version for building the kernel up to 4.8.
> 
> Series applied to sparc-next, thanks Will.

Thanks, although this was picked up by -tip a couple of days ago [1] since
the READ_ONCE() rework relies on it to avoid breaking the sparc32 build.

It's obviously harmless to go in both trees, but if you don't need it for
anything then you may want to drop these to avoid duplicate commits in
mainline.

Cheers,

Will

[1] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=locking/kcsan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ