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: <20161030181632.GB2574@sasha-lappy>
Date:   Sun, 30 Oct 2016 14:16:32 -0400
From:   "Levin, Alexander" <alexander.levin@...izon.com>
To:     Al Viro <viro@...IV.linux.org.uk>
Cc:     Joe Korty <joe.korty@...current.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Levin, Alexander" <alexander.levin@...izon.com>
Subject: Re: [4.1 backport trouble] Re: BUGreport: fix minor infoleak in
 get_user_ex()

On Thu, Oct 27, 2016 at 10:02:10PM -0400, Al Viro wrote:
> ... and frankly, backporting 548acf19234d would be my preference.  It's a bit
> more intrusive than needed (_ASM_EXTABLE_FAULT is used only in memcpy_mcsafe(),
> which is used only by pmem and it's the only reason for passing the trap
> number to fixup_exception()), but AFAICS it's fairly safe.  Objections?

I've grabbed 548acf19234d for 4.1, thanks!

-- 

Thanks,
Sasha

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ