mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ruben Wauters <rubenru09@aol.com>
To: YuanZhe Liu <25031212351@stu.xidian.edu.cn>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Noralf Trønnes" <noralf@tronnes.org>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, "Bin Yu" <byu@xidian.edu.cn>,
	"Cheng Wen" <wencheng@xidian.edu.cn>
Subject: Re: [PATCH] drm/gud: avoid divide error in gud_stats_debugfs
Date: Fri, 30 Oct 2026 22:07:14 +0000	[thread overview]
Message-ID: <962581aca91290526f4cac2330fa97b4311051b4.camel@aol.com> (raw)
In-Reply-To: <20261029073311.14556-1-25031212351@stu.xidian.edu.cn>

[-- Attachment #1: Type: text/plain, Size: 2783 bytes --]

On Thu, 2026-10-29 at 15:33 +0800, YuanZhe Liu wrote:
> gud_stats_debugfs() computes the compression ratio by dividing the
> accumulated uncompressed length by stats_actual_length. That counter
> is
> zero until the first framebuffer flush has completed, so reading the
> stats debugfs file on a display which negotiates LZ4 compression
> raises
> a divide error before any frame has been sent. The wrap-around reset
> in
> gud_flush_rect() also clears the counter for a moment, which a
> concurrent read can observe.
> 
> Copy the counter into a local variable and skip the ratio computation
> when it is zero.
> 
> Fixes: 40e1a70b4aed ("drm: Add GUD USB Display driver")
> Cc: stable@vger.kernel.org
> Co-developed-by: Bin Yu <byu@xidian.edu.cn>
> Signed-off-by: Bin Yu <byu@xidian.edu.cn>
> Co-developed-by: Cheng Wen <wencheng@xidian.edu.cn>
> Signed-off-by: Cheng Wen <wencheng@xidian.edu.cn>
> Signed-off-by: YuanZhe Liu <25031212351@stu.xidian.edu.cn>
Acked-by: Ruben Wauters <rubenru09@aol.com>

Sashiko highlighted a potential issue with reading stats_actual_length
twice when a flush_rect occurs between them. This *could* still trigger
a divide error, however, this implementation is still better than
current. The best thing to do would be to put a READ_ONCE when
stats_actual_length is read.

This patch is better than the current implementation, and I don't think
many compilers would optimise it to two memory reads? But it is
possible, and compiler optimisation is a fairly complicated topic, so
if you do wish you can add the READ_ONCE, but I'm also happy for it to
go in without, as it is better than current.

Ruben
> ---
>  drivers/gpu/drm/gud/gud_drv.c | 13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/gud/gud_drv.c
> b/drivers/gpu/drm/gud/gud_drv.c
> index 3a1b9e2a2eaa..85ddb302d2ba 100644
> --- a/drivers/gpu/drm/gud/gud_drv.c
> +++ b/drivers/gpu/drm/gud/gud_drv.c
> @@ -329,10 +329,17 @@ static int gud_stats_debugfs(struct seq_file
> *m, void *data)
>  	seq_puts(m, "\n");
>  
>  	if (gdrm->compression) {
> +		u64 actual_length = gdrm->stats_actual_length;
>  		u64 remainder;
> -		u64 ratio = div64_u64_rem(gdrm->stats_length, gdrm-
> >stats_actual_length,
> -					  &remainder);
> -		u64 ratio_frac = div64_u64(remainder * 10, gdrm-
> >stats_actual_length);
> +		u64 ratio, ratio_frac;
> +
> +		if (!actual_length) {
> +			seq_puts(m, "Compression ratio: n/a\n");
> +			return 0;
> +		}
> +
> +		ratio = div64_u64_rem(gdrm->stats_length,
> actual_length, &remainder);
> +		ratio_frac = div64_u64(remainder * 10,
> actual_length);
>  
>  		seq_printf(m, "Compression ratio: %llu.%llu\n",
> ratio, ratio_frac);
>  	}

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 1028 bytes --]

  reply	other threads:[~2026-10-30 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  7:33 YuanZhe Liu
2026-10-30 22:07 ` Ruben Wauters [this message]
2026-11-12  4:53   ` Ruben Wauters

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=962581aca91290526f4cac2330fa97b4311051b4.camel@aol.com \
    --to=rubenru09@aol.com \
    --cc=25031212351@stu.xidian.edu.cn \
    --cc=airlied@gmail.com \
    --cc=byu@xidian.edu.cn \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=noralf@tronnes.org \
    --cc=simona@ffwll.ch \
    --cc=stable@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=wencheng@xidian.edu.cn \
    /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®