From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Shile Zhang <shile.zhang@linux.alibaba.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Wen Kang <kw01107137@alibaba-inc.com>,
stable@vger.kernel.org,
virtualization@lists.linux-foundation.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.10.y] drm/cirrus: fix a NULL vs IS_ERR() checks
Date: Mon, 25 Apr 2022 12:36:05 +0200 [thread overview]
Message-ID: <YmZ5lZMkjo3XlYdN@kroah.com> (raw)
In-Reply-To: <550e9439-adf6-3df8-41a0-9a7ee5447907@linux.alibaba.com>
On Sun, Apr 24, 2022 at 11:27:17AM +0800, Shile Zhang wrote:
> Hi David and Daniel,
>
> Sorry but could you please help to check this issue?
> Due to the function 'drm_gem_shmem_vmap' could return ERROR pointers which
> will cause the kernel crash due to 'cirrus_fb_blit_rect' only check the
> pointer.
>
> Since the related code has been refactoring in mainline, so this issue only
> happened in stable 5.10.y branch.
>
> @Greg
> I think it is probably not realistic to backport the related refactoring
> from mainline directly, so I just give this bugfix patch only for 5.10.y
> branch.
I'm sorry, but I do not have "this bugfix" in my queue anymore,
considering it is so old. Please rebase and resubmit.
thanks,
greg k-h
prev parent reply other threads:[~2022-04-25 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211228132556.108711-1-shile.zhang@linux.alibaba.com>
[not found] ` <YcsWcqVN7Dwue1I2@kroah.com>
[not found] ` <f4dedbfc-0cca-a6cb-996b-4bd928008269@linux.alibaba.com>
[not found] ` <YcsZqU8M11elHqg3@kroah.com>
[not found] ` <1cc25ebe-2c68-458b-15a2-fc4c80ba2054@linux.alibaba.com>
[not found] ` <Ycshhu6pXC4Pt1YK@kroah.com>
[not found] ` <c74d61a5-31dc-0946-5a35-e1a4cd549b6e@linux.alibaba.com>
[not found] ` <YcxjGDxgF+mA7vLY@kroah.com>
[not found] ` <ae3ebd93-e3c0-ec2e-24be-07241b558b5e@linux.alibaba.com>
2022-04-24 3:27 ` Shile Zhang
2022-04-25 10:36 ` Greg Kroah-Hartman [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=YmZ5lZMkjo3XlYdN@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kw01107137@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shile.zhang@linux.alibaba.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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
Powered by JetHome