From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Walter Wu <walter-zh.wu@mediatek.com>,
wsd_upstream <wsd_upstream@mediatek.com>,
LKML <linux-kernel@vger.kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
Linux-MM <linux-mm@kvack.org>,
Alexander Potapenko <glider@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] kasan: detect negative size in memory operation function
Date: Mon, 11 Nov 2019 11:24:36 +0300 [thread overview]
Message-ID: <20df03c5-e733-98b0-84e9-8d52ddce5c98@virtuozzo.com> (raw)
In-Reply-To: <CACT4Y+bfGrJemwyMVqd2Kt19mF2i=3GwXRKHP0qGJaT_5OhSCA@mail.gmail.com>
On 11/11/19 10:57 AM, Dmitry Vyukov wrote:
> On Fri, Nov 8, 2019 at 11:32 PM Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
>>> diff --git a/mm/kasan/generic_report.c b/mm/kasan/generic_report.c
>>> index 36c645939bc9..52a92c7db697 100644
>>> --- a/mm/kasan/generic_report.c
>>> +++ b/mm/kasan/generic_report.c
>>> @@ -107,6 +107,24 @@ static const char *get_wild_bug_type(struct kasan_access_info *info)
>>>
>>> const char *get_bug_type(struct kasan_access_info *info)
>>> {
>>> + /*
>>> + * If access_size is negative numbers, then it has three reasons
>>> + * to be defined as heap-out-of-bounds bug type.
>>> + * 1) Casting negative numbers to size_t would indeed turn up as
>>> + * a large size_t and its value will be larger than ULONG_MAX/2,
>>> + * so that this can qualify as out-of-bounds.
>>> + * 2) If KASAN has new bug type and user-space passes negative size,
>>> + * then there are duplicate reports. So don't produce new bug type
>>> + * in order to prevent duplicate reports by some systems
>>> + * (e.g. syzbot) to report the same bug twice.
>>> + * 3) When size is negative numbers, it may be passed from user-space.
>>> + * So we always print heap-out-of-bounds in order to prevent that
>>> + * kernel-space and user-space have the same bug but have duplicate
>>> + * reports.
>>> + */
>>
>> Completely fail to understand 2) and 3). 2) talks something about *NOT* producing new bug
>> type, but at the same time you code actually does that.
>> 3) says something about user-space which have nothing to do with kasan.
>
> The idea was to use one of the existing bug titles so that syzbot does
> not produce 2 versions for OOBs where size is user-controlled. We
> don't know if it's overflow from heap, global or stack, but heap is
> the most common bug, so saying heap overflow will reduce chances of
> producing duplicates the most.
> But for all of this to work we do need to use one of the existing bug titles.
The "heap-out-of-bounds" is not one of the existing bug titles.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-11 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 2:05 [PATCH v3 1/2] kasan: detect negative size in memory operation function Walter Wu
2019-11-08 22:31 ` Andrey Ryabinin
2019-11-11 7:14 ` Walter Wu
2019-11-11 9:29 ` Andrey Ryabinin
2019-11-11 10:12 ` Walter Wu
2019-11-11 10:17 ` Dmitry Vyukov
2019-11-11 10:28 ` Walter Wu
2019-11-11 7:57 ` Dmitry Vyukov
2019-11-11 8:24 ` Andrey Ryabinin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-24 8:57 Walter Wu
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=20df03c5-e733-98b0-84e9-8d52ddce5c98@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=walter-zh.wu@mediatek.com \
--cc=wsd_upstream@mediatek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).