From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Matthew Wilcox <willy@infradead.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: [PATCH 1/1] container_of: Document container_of_const() is preferred
Date: Mon, 17 Jun 2024 13:08:25 +0300 [thread overview]
Message-ID: <20240617100825.2510728-1-sakari.ailus@linux.intel.com> (raw)
There is a warning in kerneldoc documentation of container_of() that
constness of @ptr is lost. While this is a suggestion container_of_const()
should be used instead, the vast majority of new code still uses
container_of():
$ git diff v6.8 v6.9|grep container_of\(|wc -l
788
$ git diff v6.8 v6.9|grep container_of_const|wc -l
11
Make an explicit recommendation to use container_of_const(), unless @ptr
is const but its container isn't.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
include/linux/container_of.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/linux/container_of.h b/include/linux/container_of.h
index 713890c867be..7563015ff165 100644
--- a/include/linux/container_of.h
+++ b/include/linux/container_of.h
@@ -13,7 +13,9 @@
* @type: the type of the container struct this is embedded in.
* @member: the name of the member within the struct.
*
- * WARNING: any const qualifier of @ptr is lost.
+ * WARNING: any const qualifier of @ptr is lost. container_of() should only be
+ * used in cases where @ptr is const and its container is not and you know what
+ * you're doing. Otherwise always use container_of_const().
*/
#define container_of(ptr, type, member) ({ \
void *__mptr = (void *)(ptr); \
--
2.39.2
next reply other threads:[~2024-06-17 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 10:08 Sakari Ailus [this message]
2024-06-17 10:44 ` Greg Kroah-Hartman
2024-06-18 9:09 ` Sakari Ailus
2024-06-18 10:01 ` Greg Kroah-Hartman
2024-06-18 11:52 ` Sakari Ailus
2024-06-18 12:54 ` Greg Kroah-Hartman
2024-06-18 13:56 ` Matthew Wilcox
2024-06-18 14:02 ` Greg Kroah-Hartman
2024-08-09 12:59 ` Andy Shevchenko
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=20240617100825.2510728-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=willy@infradead.org \
/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®