linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
To: ryabinin.a.a@gmail.com, andreyknvl@gmail.com, elver@google.com
Cc: arnd@kernel.org, glider@google.com, dvyukov@google.com,
	vincenzo.frascino@arm.com, akpm@linux-foundation.org,
	kasan-dev@googlegroups.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, snovitoll@gmail.com
Subject: [PATCH 0/2] kasan: few improvements on kunit tests
Date: Fri,  1 Nov 2024 23:40:09 +0500	[thread overview]
Message-ID: <20241101184011.3369247-1-snovitoll@gmail.com> (raw)

This patch series addresses the issue [1] with KASAN symbols used
in the Kunit test, but exported as EXPORT_SYMBOL_GPL.

Also a small tweak of marking kasan_atomics() as KUNIT_CASE_SLOW
to avoid kunit report that the test should be marked as slow.

Both patches have been tested on (CONFIG_KASAN_KUNIT_TEST=y):
- x86_64: CONFIG_KASAN=y
- arm64: CONFIG_KASAN_HW_TAGS=y

[1] https://lore.kernel.org/linux-mm/ZxigQIF59s3_h5PS@infradead.org/T/

EXPORT_SYMBOL_IF_KUNIT

Sabyrzhan Tasbolatov (2):
  kasan: use EXPORT_SYMBOL_IF_KUNIT to export symbols for kunit tests
  kasan: change kasan_atomics kunit test as KUNIT_CASE_SLOW

 mm/kasan/hw_tags.c      |  7 ++++---
 mm/kasan/kasan_test_c.c |  4 +++-
 mm/kasan/report.c       | 17 +++++++++--------
 3 files changed, 16 insertions(+), 12 deletions(-)

-- 
2.34.1



             reply	other threads:[~2024-11-01 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 18:40 Sabyrzhan Tasbolatov [this message]
2024-11-01 18:40 ` [PATCH 1/2] kasan: use EXPORT_SYMBOL_IF_KUNIT to export symbols Sabyrzhan Tasbolatov
2024-11-01 23:38   ` Andrey Konovalov
2024-11-01 18:40 ` [PATCH 2/2] kasan: change kasan_atomics kunit test as KUNIT_CASE_SLOW Sabyrzhan Tasbolatov
2024-11-01 23:38   ` Andrey Konovalov

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=20241101184011.3369247-1-snovitoll@gmail.com \
    --to=snovitoll@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=arnd@kernel.org \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ryabinin.a.a@gmail.com \
    --cc=vincenzo.frascino@arm.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