mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Farhad Alemi <farhad.alemi@berkeley.edu>,
	Jiri Kosina <jikos@kernel.org>,
	 Benjamin Tissoires	 <bentiss@kernel.org>,
	Zhang Lixu <lixu.zhang@intel.com>
Cc: falemi@asu.edu, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] ish_hw_start -- page fault on a PIO cookie: intel_ish_ipc maps an I/O BAR and dereferences it
Date: Fri, 28 Aug 2026 08:45:11 -0700	[thread overview]
Message-ID: <42d7b3ad68ed7870e141fcfa62a483356e7c5b7f.camel@linux.intel.com> (raw)
In-Reply-To: <CA+0ovCgaya8JEc4xmBKPbe5AbrPuaK0tUKxuOxQYMsPTQT1ALw@mail.gmail.com>

Hi Farhad,

On Thu, 2026-08-27 at 22:36 -0700, Farhad Alemi wrote:
> Hello,
> 
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
> 
>  
> https://github.com/farhad-alemi/public_bug_reports/tree/main/152-hid-intel-ish-ioport-bar-deref/
> 
>   BUG: unable to handle page fault for address: 000000000001c078
>   #PF: supervisor read access in kernel mode
>   #PF: error_code(0x0000) - not-present page
>   Oops: Oops: 0000 [#1] SMP KASAN NOPTI
>   RIP: 0010:ish_hw_start+0x41/0x2d0
>   Call Trace:
>    <TASK>
>    ish_probe+0x34d/0x460
>    pci_device_probe+0x436/0xc90
>    really_probe+0x267/0xaf0
>    __driver_probe_device+0x1e2/0x350
>    driver_probe_device+0x4f/0x240
>    __device_attach_driver+0x270/0x410
>    bus_for_each_drv+0x258/0x2f0
>    __device_attach+0x2c5/0x450
>    drivers_probe_store+0x11c/0x220
> 
> Our reproducer.c is available upon request.
> 
> Happy to test a patch if that would help.

Thanks for reporting.

Please submit a patch.
https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html

Thanks,
Srinivas

> 
> Regards,

      reply	other threads:[~2026-08-28 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  5:36 Farhad Alemi
2026-08-28 15:45 ` srinivas pandruvada [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=42d7b3ad68ed7870e141fcfa62a483356e7c5b7f.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=bentiss@kernel.org \
    --cc=falemi@asu.edu \
    --cc=farhad.alemi@berkeley.edu \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixu.zhang@intel.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
all inboxes | Powered by JetHome®