From: sashiko-bot@kernel.org
To: xujiahao <xujiahao@cmss.chinamobile.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/fbdev-shmem: don't warn on a transient dirty callback failure
Date: Wed, 11 Nov 2026 03:52:01 +0000 [thread overview]
Message-ID: <sashiko-outbox-208238@kernel.org> (raw)
In-Reply-To: <20261111114108.675721-1-xujiahao@cmss.chinamobile.com>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [High] drm/fbdev-shmem: single-word handle used in Author and
Signed-off-by
- [Low] drm/fbdev-shmem: missing Fixes trailer for
drm_fbdev_shmem_helper_fb_dirty()
--
commit 3bcd442074e2ca85eb8c3537eb31d873b7b1b756
Author: xujiahao <xujiahao@cmss.chinamobile.com>
> drm/fbdev-shmem: don't warn on a transient dirty callback failure
>
> The fbdev dirty callback (drm_atomic_helper_dirtyfb()) can fail with
> -ENOMEM when the atomic commit allocation fails under memory pressure.
> That is a transient runtime condition, not a driver bug: the damage is
> only cosmetic and the frame is redrawn on the next flush.
>
> drm_WARN_ONCE() turns this recoverable failure into a WARN splat (and a
> panic with panic_on_warn), which syzbot keeps reporting:
>
> virtio-pci 0000:00:01.0: [drm] Dirty helper failed: ret=-12
> WARNING: drivers/gpu/drm/drm_fbdev_shmem.c:118 at ...
>
> Keep the warning for other failures, but do not warn about -ENOMEM. The
> error is still propagated to the caller.
>
> Reported-by: syzbot+369ee6a6e9d0bbf14b37@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=369ee6a6e9d0bbf14b37
> Signed-off-by: xujiahao <xujiahao@cmss.chinamobile.com>
[Severity: High]
Both the Author field and the Signed-off-by trailer use the single-word
handle "xujiahao" instead of a full real name. Per
Documentation/process/submitting-patches.rst, the Developer's Certificate of
Origin requires signing off with a full human name (for example, "Jiahao
Xu").
[Severity: Low]
This fixes a false-positive warning in drm_fbdev_shmem_helper_fb_dirty().
Should the commit message include a Fixes: trailer?
Fixes: 150f431a0831 ("drm/fbdev: Add fbdev-shmem")
Fixes: f0f195d1a3ae ("drm/fbdev-shmem: Support struct drm_driver.fbdev_probe")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111114108.675721-1-xujiahao@cmss.chinamobile.com?part=1
prev parent reply other threads:[~2026-11-11 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:41 [PATCH] drm/fbdev-shmem: don't warn on a transient dirty callback failure xujiahao
2026-11-11 3:52 ` sashiko-bot [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=sashiko-outbox-208238@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xujiahao@cmss.chinamobile.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.