mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	kunit-dev@googlegroups.com, lkft-triage@lists.linaro.org,
	David Gow <davidgow@google.com>,
	Brendan Higgins <brendan.higgins@linux.dev>,
	Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next: kasan: Unable to handle kernel paging request at virtual address
Date: Wed, 8 May 2024 16:38:45 +0300	[thread overview]
Message-ID: <3a2e5e75-66d4-4411-aa8c-b028259fe8f6@moroto.mountain> (raw)
In-Reply-To: <CA+G9fYvOjtEBtB21FwFmvbautebx_2Py-tjqduPcWyS5B9nB5w@mail.gmail.com>

On Wed, May 08, 2024 at 04:59:10PM +0530, Naresh Kamboju wrote:
> While running kunit tests on arm64 and x86_64 the following kernel BUG
> noticed on running Linux next-20240508 kernel and stride tests failed.
> 
> observations:
> 1) The null pointer dereference notice while running kunit_test
> 2) The stride test case failed on today's linux next-20240508 tag.
> 
> The detailed log provided in the links below.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Crash log:
> --------
> 
> <6>[   43.086497]     KTAP version 1
> <6>[   43.087004]     # Subtest: kunit_fault
> <6>[   43.087577]     # module: kunit_test
> <6>[   43.087748]     1..1
> <1>[   43.092588] Unable to handle kernel paging request at virtual
> address dfff800000000000
> <1>[   43.093687] KASAN: null-ptr-deref in range
> [0x0000000000000000-0x0000000000000007]
> <1>[   43.094770] Mem abort info:
> <1>[   43.095425]   ESR = 0x0000000096000005
> <1>[   43.097071]   EC = 0x25: DABT (current EL), IL = 32 bits
> <1>[   43.098034]   SET = 0, FnV = 0
> <1>[   43.098542]   EA = 0, S1PTW = 0
> <1>[   43.099104]   FSC = 0x05: level 1 translation fault
> <1>[   43.099837] Data abort info:
> <1>[   43.100679]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
> <1>[   43.101535]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> <1>[   43.102321]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> <1>[   43.103287] [dfff800000000000] address between user and kernel
> address ranges
> <0>[   43.105111] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
> <4>[   43.106046] Modules linked in:
> <4>[   43.108961] CPU: 1 PID: 375 Comm: kunit_try_catch Tainted: G
>             N 6.9.0-rc7-next-20240508 #1
> <4>[   43.110433] Hardware name: linux,dummy-virt (DT)
> <4>[   43.111555] pstate: 82400009 (Nzcv daif +PAN -UAO +TCO -DIT
> -SSBS BTYPE=--)
> <4>[   43.113232] pc : kunit_test_null_dereference+0x2c/0x114
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
This function is supposed to dereference a NULL pointer.

regards,
dan carpenter


      reply	other threads:[~2024-05-08 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 11:29 Naresh Kamboju
2024-05-08 13:38 ` Dan Carpenter [this message]

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=3a2e5e75-66d4-4411-aa8c-b028259fe8f6@moroto.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=brendan.higgins@linux.dev \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.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

all inboxes | Powered by JetHome®