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  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:	Mon, 22 Dec 2014 14:39:54 -0600
From: (Eric W. Biederman)
To:	Sasha Levin <>
Cc:	Andrey Ryabinin <>,
	LKML <>,
	linux-fsdevel <>,
	Al Viro <>,
	"davej \\>\> Dave Jones" <>
Subject: Re: fs: proc: gpf in find_entry

Sasha Levin <> writes:

> On 12/22/2014 12:52 PM, Andrey Ryabinin wrote:
>> 2014-12-22 18:51 GMT+03:00 Eric W. Biederman <>:
>>> These two instructions:
>>>>>   11:   4d 85 ff                test   %r15,%r15
>>>>>   14:   0f 84 de 01 00 00       je     0x1f8
>>> Should prevent a NULL %r15 value from ever reaching the trapping
>>> instruction.
>> If they were executed, then yes. But I think there was jump from somewhere
>> to the instructions below those two.
> There is indeed a jump direct to that point, which avoids the %r15
> check.

Where do you see that direct jump, that certainly has not been posted
in this thread?

There are certainly no such code paths I in the source code.  There is
only one NULL pointer check in find_entry and it is executed every time
the loop executes.

So at this point all I know is some set of tools has totally destroyed
the code and made what Sasha Levin's is testing so far from the source
code that this is a useless bug report.

I have no reason to even suspect this bug is actually in the upstream

This appears to be a kind of testing that slows development and wastes
peoples time.  Can someone give me a patch that sets the TAINTED flag
when KASAN is loaded?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists