Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: 김강민 <km.kim1503@gmail.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, jani.nikula@linux.intel.com,
	rodrigo.vivi@intel.com, tursulin@ursulin.net, airlied@gmail.com,
	simona@ffwll.ch, andi.shyti@linux.intel.com,
	ville.syrjala@linux.intel.com, nitin.r.gote@intel.com,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	syzkaller@googlegroups.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in eb_release_vmas
Date: Wed, 1 Oct 2025 14:00:29 +0200	[thread overview]
Message-ID: <aN0X3ck-egLMn_Xy@ashyti-mobl2.lan> (raw)
In-Reply-To: <CAGfirfdDe879wFzABVZkTV7grEimpnc0XrrKpj2SX1w_TLtgNg@mail.gmail.com>

On Wed, Oct 01, 2025 at 12:14:41AM +0900, 김강민 wrote:
> Ok, I will do it.

when you do, can you please paste the link here?

Thanks,
Andi

> Best Regards,
> GangMin Kim.
> 
> 2025년 9월 30일 (화) 오후 6:17, Joonas Lahtinen
> <joonas.lahtinen@linux.intel.com>님이 작성:
> >
> > Hi,
> >
> > Can you please open a bug as per the instructions in:
> >
> > https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
> >
> > Thanks in advance!
> >
> > Regards, Joonas

  reply	other threads:[~2025-10-01 12:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfirffPy5biFVLtSNEW60UCXa6_=-=NrQbU7iLQ8+BXnFQ=1A@mail.gmail.com>
2025-09-22 14:03 ` BUG: unable to handle kernel NULL pointer dereference in eb_release_vmas Tvrtko Ursulin
2025-09-30  9:16 ` Joonas Lahtinen
2025-09-30 15:14   ` 김강민
2025-10-01 12:00     ` Andi Shyti [this message]
     [not found]       ` <CAGfirffg4JzGkwaKTm9fL9Nyud4kBALvfW3Et33ZF60e8cVO1g@mail.gmail.com>
2025-10-07  6:29         ` 김강민
2025-10-09  9:08           ` Jani Nikula

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=aN0X3ck-egLMn_Xy@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=km.kim1503@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitin.r.gote@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=syzkaller@googlegroups.com \
    --cc=tursulin@ursulin.net \
    --cc=ville.syrjala@linux.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