From: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
To: aryabinin@virtuozzo.com, Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Cc: kasan-dev@googlegroups.com, lkml <linux-kernel@vger.kernel.org>
Subject: BUG: KASAN lib/test_kasan.c
Date: Sat, 05 Dec 2020 00:26:10 +0530 [thread overview]
Message-ID: <dc46ab93e6b08fa6168591c7f6345b9dc91a81bb.camel@rajagiritech.edu.in> (raw)
hello,
detected KASAN BUG
[ related information ]
-------------------x-------------------x------------------------>
[ 43.616259] BUG: KASAN: vmalloc-out-of-bounds in
vmalloc_oob+0x146/0x2c0
(gdb) l *vmalloc_oob+0x146/0x2c0
0xffffffff81b8b0b0 is in vmalloc_oob (lib/test_kasan.c:764).
759 kfree_sensitive(ptr);
760 KUNIT_EXPECT_KASAN_FAIL(test, kfree_sensitive(ptr));
761 }
762
763 static void vmalloc_oob(struct kunit *test)
764 {
765 void *area;
766
767 if (!IS_ENABLED(CONFIG_KASAN_VMALLOC)) {
768 kunit_info(test, "CONFIG_KASAN_VMALLOC is not
enabled.");
(gdb) l *vmalloc_oob+0x146
0xffffffff81b8b1f6 is in vmalloc_oob (lib/test_kasan.c:779).
774 * The MMU will catch that and crash us.
775 */
776 area = vmalloc(3000);
777 KUNIT_ASSERT_NOT_ERR_OR_NULL(test, area);
778
779 KUNIT_EXPECT_KASAN_FAIL(test, ((volatile char
*)area)[3100]);
780 vfree(area);
781 }
782
783 static struct kunit_case kasan_kunit_test_cases[] = {
----------------x-----------------------------x-------------------->
Reported by: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
--
software engineer
rajagiri school of engineering and technology - autonomous
next reply other threads:[~2020-12-04 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 18:56 Jeffrin Jose T [this message]
2020-12-04 20:29 ` BUG: KASAN lib/test_kasan.c Marco Elver
2020-12-04 20:52 ` Jeffrin Jose T
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=dc46ab93e6b08fa6168591c7f6345b9dc91a81bb.camel@rajagiritech.edu.in \
--to=jeffrin@rajagiritech.edu.in \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
/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).