All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC v5 1/3] workqueue: Simplify unbound sysfs attribute registration
Date: Wed, 23 Sep 2026 16:22:00 +0000	[thread overview]
Message-ID: <20260923162200.DFC951F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923161251.45428-2-tvrtko.ursulin@igalia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] workqueue: ABI breakage by renaming sysfs attr affinity_scope to affn_scope
--

commit 2efe6031e6371199ddd3b670919f910c5c5f043a
Author: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>

workqueue: Simplify unbound sysfs attribute registration

This commit simplifies the registration of unbound workqueue sysfs attributes.
It replaces manual attribute registration loops with an attribute group
visibility check handled by the device core. This streamlines both registration
and error unwinding.

> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 8fb31947c4c7a..a9e96329547c9 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c

[ ... ]

> -static struct device_attribute wq_sysfs_unbound_attrs[] = {
> -	__ATTR(nice, 0644, wq_nice_show, wq_nice_store),
> -	__ATTR(cpumask, 0644, wq_cpumask_show, wq_cpumask_store),
> -	__ATTR(affinity_scope, 0644, wq_affn_scope_show, wq_affn_scope_store),
> -	__ATTR(affinity_strict, 0644, wq_affinity_strict_show, wq_affinity_strict_store),
> -	__ATTR_NULL,
> +static DEVICE_ATTR_RW(nice);
> +static DEVICE_ATTR_RW(affn_scope);

[Severity: High]
Does this change the userspace ABI by renaming the sysfs file?

The previous code exposed this attribute to userspace as affinity_scope.
Using DEVICE_ATTR_RW(affn_scope) implicitly sets the sysfs file name to
affn_scope instead of the original affinity_scope.

Will this cause userspace tools or scripts expecting to find the
/sys/bus/workqueue/devices/*/affinity_scope file to fail?

> +static DEVICE_ATTR_RW(affinity_strict);
> +/* Avoid naming clash with the other cpumask */
> +static struct device_attribute dev_attr_unbound_cpumask =
> +	__ATTR(cpumask, 0644, unbound_cpumask_show, unbound_cpumask_store);
> +
> +static struct attribute *wq_sysfs_unbound_attrs[] = {
> +	&dev_attr_nice.attr,
> +	&dev_attr_unbound_cpumask.attr,
> +	&dev_attr_affn_scope.attr,
> +	&dev_attr_affinity_strict.attr,
> +	NULL,
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260923161251.45428-1-tvrtko.ursulin@igalia.com?part=1

  reply	other threads:[~2026-09-23 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 16:12 [RFC v5 0/3] Realtime workqueues and panthor realtime submission Tvrtko Ursulin
2026-09-23 16:12 ` [RFC v5 1/3] workqueue: Simplify unbound sysfs attribute registration Tvrtko Ursulin
2026-09-23 16:22   ` sashiko-bot [this message]
2026-09-23 17:12   ` Tvrtko Ursulin
2026-09-23 16:12 ` [RFC v5 2/3] workqueue: Add support for real-time workers Tvrtko Ursulin
2026-09-23 16:25   ` sashiko-bot
2026-09-29  0:00   ` Tejun Heo
2026-10-01  9:22     ` Tvrtko Ursulin
2026-09-23 16:12 ` [RFC v5 3/3] drm/panthor: Create per queue priority workqueues Tvrtko Ursulin

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=20260923162200.DFC951F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tvrtko.ursulin@igalia.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.