public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zheng Hacker <hackerzheng666@gmail.com>
Cc: Zhenyu Wang <zhenyuw@linux.intel.com>,
	alex000young@gmail.com, security@kernel.org,
	dri-devel@lists.freedesktop.org, tvrtko.ursulin@linux.intel.com,
	airlied@linux.ie, intel-gfx@lists.freedesktop.org,
	joonas.lahtinen@linux.intel.com, linux-kernel@vger.kernel.org,
	xmzyshypnc <1002992920@qq.com>,
	jani.nikula@linux.intel.com, daniel@ffwll.ch,
	rodrigo.vivi@intel.com, intel-gvt-dev@lists.freedesktop.org,
	zhi.a.wang@intel.com
Subject: Re: [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry.
Date: Thu, 8 Sep 2022 11:19:11 +0200	[thread overview]
Message-ID: <Yxmzj2nCoTKurCY8@kroah.com> (raw)
In-Reply-To: <CAJedcCxO_Rq0qMeLiHtY5+FuN1A1pDGsZd3gMtvUpm1xbAK3aA@mail.gmail.com>

On Thu, Sep 08, 2022 at 05:09:40PM +0800, Zheng Hacker wrote:
> Hi Zhenyu,
> 
> This issue has been open for a few days. Could you plz write a patch
> for that :) I'm not familiar with the logical code here.

As this is only able to be hit in a theoretical system, it isn't that
high of a priority, if any priority at all.  Why not try to write a
patch for it yourself to help resolve the issue faster?

thanks,

greg k-h

  reply	other threads:[~2022-09-08  9:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_E1BBF05904DFB73C478DCD592740AAE0780A@qq.com>
     [not found] ` <CAJedcCxVW++iH49UFZp9ruUuTcNubWCH6Wsqe11K4COB3E8msg@mail.gmail.com>
2022-09-05  7:35   ` [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry Zheng Hacker
2022-09-05  7:46     ` Zheng Hacker
2022-09-05  8:04       ` Greg KH
2022-09-05  8:53         ` Alex Young
2022-09-06 11:36         ` Zheng Hacker
2022-09-07  3:07           ` Zhenyu Wang
2022-09-07  6:47             ` Zheng Hacker
2022-09-08  9:09             ` Zheng Hacker
2022-09-08  9:19               ` Greg KH [this message]
     [not found]                 ` <CAJedcCwVC6Rg+wF7h6GhFvL6BGkKV=DS9Mo9fOf-gfDAk9VqPg@mail.gmail.com>
2022-09-16  6:39                   ` Zheng Hacker
2022-09-16  6:40                     ` Zheng Hacker
2022-09-16  8:25                     ` Greg KH
2022-09-16 15:21                       ` Zheng Hacker
2022-09-16 15:54                       ` Zheng Hacker
2022-09-17  9:08                         ` Greg KH
2022-09-18 17:17                           ` Zheng Hacker
     [not found] <tencent_ED24158E83CB9885E8BDD173EB5896B51906@qq.com>
2022-09-19  9:30 ` Jani Nikula
2022-09-19  9:55   ` Zheng Hacker
2022-09-21  9:13   ` Zheng Hacker

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=Yxmzj2nCoTKurCY8@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=1002992920@qq.com \
    --cc=airlied@linux.ie \
    --cc=alex000young@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hackerzheng666@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=security@kernel.org \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhi.a.wang@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