All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: David Gow <davidgow@google.com>, Will Deacon <will@kernel.org>,
	mic@digikod.net, keescook@chromium.org, rmoar@google.com,
	lkft-triage@lists.linaro.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@redhat.com, longman@redhat.com, boqun.feng@gmail.com,
	anders.roxell@linaro.org, arnd@arndb.de, linux@roeck-us.net,
	Linux Kernel Functional Testing <lkft@linaro.org>
Subject: Re: BUG: KASAN: null-ptr-deref in _raw_spin_lock_irq next-20240410
Date: Thu, 11 Apr 2024 18:00:25 +0300	[thread overview]
Message-ID: <f2d02e35-185e-44d1-9b58-1034336e2e0d@moroto.mountain> (raw)
In-Reply-To: <CA+G9fYt6U4YzYGvYWxDVvUVKNc0pgVYiGafZ5_OSEf=5r1=YYA@mail.gmail.com>

On Thu, Apr 11, 2024 at 08:20:55PM +0530, Naresh Kamboju wrote:
> 
> I use to notice kernel panic while running kunit tests
> now I have noticed this
> 
> Unable to handle kernel paging request at virtual address
> KASAN: null-ptr-deref in range
> pc : kunit_test_null_dereference (lib/kunit/kunit-test.c:119)
> lr : kunit_generic_run_threadfn_adapter (lib/kunit/try-catch.c:31)
> 
> The kunit tests run to completion and the system is stable.
> Kernel did not panic.
> 

[ Snip ]

> <0>[   76.808597] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
> <4>[   76.809876] Modules linked in:
> <4>[   76.812055] CPU: 1 PID: 567 Comm: kunit_try_catch Tainted: G
> B            N 6.9.0-rc3-next-20240410 #1
> <4>[   76.812987] Hardware name: linux,dummy-virt (DT)
> <4>[   76.814123] pstate: 12400009 (nzcV daif +PAN -UAO +TCO -DIT
> -SSBS BTYPE=--)
> <4>[ 76.814947] pc : kunit_test_null_dereference (lib/kunit/kunit-test.c:119)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is a new intentional NULL dereferencer that was added yesterday.

Maybe these should have a big printk, "Intentional NULL dereference
coming up!\n".

regards,
dan carpenter


  reply	other threads:[~2024-04-11 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 10:27 BUG: KASAN: null-ptr-deref in _raw_spin_lock_irq next-20240410 Naresh Kamboju
2024-04-10 15:23 ` Will Deacon
2024-04-10 17:14   ` Naresh Kamboju
2024-04-10 17:21     ` Naresh Kamboju
2024-04-11  4:25   ` David Gow
2024-04-11  8:48     ` Mickaël Salaün
2024-04-11 14:42     ` Naresh Kamboju
2024-04-11 14:50       ` Naresh Kamboju
2024-04-11 15:00         ` Dan Carpenter [this message]
2024-04-11 15:05           ` Guenter Roeck
2024-04-12  3:26             ` David Gow
2024-04-12  3:23     ` David Gow

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=f2d02e35-185e-44d1-9b58-1034336e2e0d@moroto.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=boqun.feng@gmail.com \
    --cc=davidgow@google.com \
    --cc=keescook@chromium.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=longman@redhat.com \
    --cc=mic@digikod.net \
    --cc=mingo@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=peterz@infradead.org \
    --cc=rmoar@google.com \
    --cc=will@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 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.