linux-kernel - Re: [PATCH 4.14 00/75] 4.14.5-stable review

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, 9 Dec 2017 08:45:44 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Ivan Kozik <ivan@...ios.org>
Cc:     linux-kernel@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        akpm@...ux-foundation.org, linux@...ck-us.net,
        Shuah Khan <shuahkh@....samsung.com>, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.14 00/75] 4.14.5-stable review

On Sat, Dec 09, 2017 at 03:34:24AM +0000, Ivan Kozik wrote:
> On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 4.14.5 release.
> > There are 75 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sat Dec  9 13:07:57 UTC 2017.
> > Anything received after that time might be too late.
> 
> I saw no problems on 8 of 9 machines, but the last one had a problem
> because it used NVIDIA drivers (387); DKMS reported:
> 
> FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only
> symbol 'ex_handler_refcount'
> //usr/src/linux-headers-4.14.0-11-common/scripts/Makefile.modpost:92:
> recipe for target '__modpost' failed
> make[3]: *** [__modpost] Error 1

Is this a new issue?  Does 4.14.4 have this issue?

> The drivers built fine after rebuilding Linux with [PATCH]
> locking/refcounts: Do not force refcount_t usage as GPL-only export
> https://lkml.org/lkml/2017/12/4/1110
> 
> which appears to be in Linus' tree as b562c171cf011d297059bd0265742eb5fab0ad2f

Odd, is 564c9cc84e2a ("locking/refcounts, x86/asm: Use unique .text
section for refcount exceptions") causing this?

thanks,

greg k-h