public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] container_of: Document container_of() is not to be used in new code
Date: Tue, 20 May 2025 17:16:45 +0300	[thread overview]
Message-ID: <aCyOzUIIvMk6Gp8o@smile.fi.intel.com> (raw)
In-Reply-To: <20250520103437.468691-1-sakari.ailus@linux.intel.com>

On Tue, May 20, 2025 at 01:34:37PM +0300, Sakari Ailus wrote:
> There is a warning in the kerneldoc documentation of container_of() that
> constness of its ptr argument is lost. While this is a faible suggestion
> container_of_const() should be used instead, the vast majority of new code
> still uses container_of():
> 
> $ git diff v6.13 v6.14|grep container_of\(|wc -l
> 646
> $ git diff v6.13 v6.14|grep container_of_const|wc -l
> 9
> 
> Make an explicit recommendation to use container_of_const().
> 
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> Hi Greg, Andy,
> 
> I guess we generally agree the additional constness check in
> container_of_const() is useful, but adding the same check to
> container_of() generates warnings -- there are some errors, too -- such as
> this one currently:
> 
> In file included from /home/sailus/src/linux/include/linux/bcma/bcma.h:14,
>                  from /home/sailus/src/linux/arch/x86/kernel/early-quirks.c:17:
> /home/sailus/src/linux/include/linux/ssb/ssb.h: In function ‘dev_to_ssb_dev’:
> /home/sailus/src/linux/include/linux/ssb/ssb.h:291:14: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
>   291 |         wrap = container_of(dev, struct __ssb_dev_wrapper, dev);
>       |              ^
> 
> As noted above, 646 new missing constness checks were introduced through
> container_of() macro use during the 6.14 cycle alone. Most of these are
> likely harmless, but with so many new users some are bound to be ignoring
> constness.
> 
> Once the warnings from bad container_of() use are worked out in a way or
> another, the constness check could be added to the container_of() macro
> and the current container_of_const() be dropped altogether.
> 
> If this patch is accepted, I'll see how to add a warning on container_of()
> to checkpatch.pl.

Hmm... Wouldn't be better to fix non-const cases and add the const check, etc
to the container_of() instead of doing these comments?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-05-20 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 10:34 [PATCH 1/1] container_of: Document container_of() is not to be used in new code Sakari Ailus
2025-05-20 14:16 ` Andy Shevchenko [this message]
2025-05-20 14:30   ` Greg Kroah-Hartman
2025-05-20 22:09     ` Sakari Ailus
2025-05-21 13:27       ` Greg Kroah-Hartman
2025-05-21 13:31         ` Greg Kroah-Hartman
2025-05-21 13:43           ` Greg Kroah-Hartman
2025-05-22 13:47           ` Greg Kroah-Hartman
2025-05-22 21:01           ` David Laight
2025-05-23  8:36             ` Greg Kroah-Hartman
2025-05-24 12:45               ` David Laight
2025-05-24 15:06                 ` Greg Kroah-Hartman

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=aCyOzUIIvMk6Gp8o@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox