mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: airlied@gmail.com, daniel@ffwll.ch,
	dri-devel@lists.freedesktop.org, ivan.orlov0322@gmail.com,
	maarten.lankhorst@linux.intel.com, skhan@linuxfoundation.org,
	tzimmermann@suse.de, Ziqi Zhao <astrajoan@yahoo.com>
Cc: syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	christian.koenig@amd.com, linaro-mm-sig@lists.linaro.org,
	glider@google.com,
	syzbot+4fad2e57beb6397ab2fc@syzkaller.appspotmail.com,
	sumit.semwal@linaro.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
Date: Fri, 08 Dec 2023 10:23:48 +0100	[thread overview]
Message-ID: <170202742812.13384.8140202310424410642.b4-ty@kernel.org> (raw)
In-Reply-To: <20230721161446.8602-1-astrajoan@yahoo.com>

On Fri, 21 Jul 2023 09:14:46 -0700, Ziqi Zhao wrote:
> The connector_set contains uninitialized values when allocated with
> kmalloc_array. However, in the "out" branch, the logic assumes that any
> element in connector_set would be equal to NULL if failed to
> initialize, which causes the bug reported by Syzbot. The fix is to use
> an extra variable to keep track of how many connectors are initialized
> indeed, and use that variable to decrease any refcounts in the "out"
> branch.
> 
> [...]

Applied to drm/drm-misc (drm-misc-fixes).

Thanks!
Maxime


  parent reply	other threads:[~2023-12-08  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230716043411.4950-1-astrajoan@yahoo.com>
2023-07-16  5:01 ` [syzbot] [dri?] KMSAN: uninit-value " syzbot
     [not found] ` <20230721161446.8602-1-astrajoan@yahoo.com>
2023-12-08  6:57   ` [PATCH] drm/crtc: Fix uninit-value bug " Harshit Mogalapalli
2023-12-08  9:23   ` Maxime Ripard [this message]
2023-12-08 13:05   ` 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=170202742812.13384.8140202310424410642.b4-ty@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=astrajoan@yahoo.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=glider@google.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=skhan@linuxfoundation.org \
    --cc=sumit.semwal@linaro.org \
    --cc=syzbot+4fad2e57beb6397ab2fc@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tzimmermann@suse.de \
    /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®