linux-kernel - Re: [PATCH AUTOSEL 4.14 72/72] string.h: fix incompatibility between FORTIFY

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]

Message-ID: <20200609115407.GA819153@kroah.com>
Date:   Tue, 9 Jun 2020 13:54:07 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@....cz>
Cc:     Daniel Axtens <dja@...ens.net>, Sasha Levin <sashal@...nel.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        David Gow <davidgow@...gle.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Daniel Micay <danielmicay@...il.com>,
        Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Alexander Potapenko <glider@...gle.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH AUTOSEL 4.14 72/72] string.h: fix incompatibility between
 FORTIFY_SOURCE and KASAN

On Tue, Jun 09, 2020 at 01:20:25PM +0200, Pavel Machek wrote:
> On Tue 2020-06-09 09:46:08, Daniel Axtens wrote:
> > Hi Sasha,
> > 
> > There's nothing inherently wrong with these patches being backported,
> > but they fix a bug that doesn't cause a crash and only affects debug
> > kernels compiled with KASAN and FORTIFY_SOURCE. Personally I wouldn't
> > change a core header file in a stable kernel for that. Perhaps I'm too
> > risk-averse.
> 
> You are in agreement with existing documentation -- stable is only for
> serious bugs.

No, lots of people run KASAN on those kernels when they are testing
their devices, this patch is fine.

thanks,

greg k-h