linux-kernel - Re: [PATCH] kernfs: handle null pointers while printing node name and path

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: <ca4bf382-afec-2838-0d07-ce93bf9b1051@yandex-team.ru>
Date:   Wed, 8 Feb 2017 16:27:33 +0300
From:   Konstantin Khlebnikov <khlebnikov@...dex-team.ru>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH] kernfs: handle null pointers while printing node name and
 path



On 08.02.2017 16:23, Greg Kroah-Hartman wrote:
> On Wed, Feb 08, 2017 at 03:59:06PM +0300, Konstantin Khlebnikov wrote:
>>
>>
>> On 08.02.2017 15:51, Greg Kroah-Hartman wrote:
>>> On Wed, Feb 08, 2017 at 02:28:55PM +0300, Konstantin Khlebnikov wrote:
>>>> Null kernfs nodes could be found at cgroups during construction.
>>>
>>> Really?  Does this happen today?  Is this an issue for older kernels as
>>> well?
>>
>> This happended again recently: https://lkml.org/lkml/2017/1/26/126
>> LTP easily crashes everything since 4.6
>
> Why did you drop the "Fixes:" and cc: stable line from the patch you
> sent me?  That would have saved me asking you this :(

No, this _was_ proposed as a fix but now bug fixed differently right in cgroups.
Now this patch just a cleanup / safer api.

>
> Care to fix this up and send a new version with that info in it?
>
> thanks,
>
> greg k-h
>