From: Sasha Levin <sasha.levin@oracle.com>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"davej @mail.xmission.com>> Dave Jones" <davej@redhat.com>
Subject: Re: fs: proc: gpf in find_entry
Date: Mon, 22 Dec 2014 13:12:21 -0500 [thread overview]
Message-ID: <54985F05.2040603@oracle.com> (raw)
In-Reply-To: <CAPAsAGwRL-fg10cPYREbXmsk09EU4qVz-3AX+OkR-QifmOW2kQ@mail.gmail.com>
On 12/22/2014 12:52 PM, Andrey Ryabinin wrote:
> 2014-12-22 18:51 GMT+03:00 Eric W. Biederman <ebiederm@xmission.com>:
>> 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.
>> What other horrible things does KASAN do to the machine code?
>>
>
> kasan insert something like following before any memory access:
>
> s8 *shadow_addr = (add >> 3) + shadow_offset;
>
> if (unlikely(*shadow_addr))
> if (unlikely(addr & 7 >= *shadow_addr))
> report_bug(addr);
>
>
> I suspect that Sasha is using kasan along with ubsan.
> In that case generated code much more horrid.
It's not *that* bad :)
Thanks,
Sasha
next prev parent reply other threads:[~2014-12-22 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 14:37 fs: proc: gpf in find_entry Sasha Levin
2014-12-22 15:31 ` Andrey Ryabinin
2014-12-22 15:51 ` Eric W. Biederman
2014-12-22 17:52 ` Andrey Ryabinin
2014-12-22 18:12 ` Sasha Levin [this message]
2014-12-22 20:39 ` Eric W. Biederman
2014-12-23 8:20 ` Andrey Ryabinin
2014-12-22 15:32 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54985F05.2040603@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.