From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
Matthew Wilcox <mawilcox@microsoft.com>,
linux-mm@kvack.org, Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v2 2/8] mm: Add kvmalloc_ab_c and kvzalloc_struct
Date: Thu, 15 Feb 2018 09:36:39 -0800 [thread overview]
Message-ID: <20180215173639.GA10146@bombadil.infradead.org> (raw)
In-Reply-To: <20180215034050.GA5775@bombadil.infradead.org>
On Wed, Feb 14, 2018 at 07:40:50PM -0800, Matthew Wilcox wrote:
> > a_foo = kvzalloc_struct_buf(struct foo, struct bar, nr_bars);
> >
> > or, of course.
> >
> > a_foo = kvzalloc_struct_buf(typeof(*a_foo), typeof(a_foo->bar[0]),
> > nr_bars);
> >
> > or whatever.
This version works, although it's more typing in the callers:
- attr_group = kvzalloc_struct(attr_group, attrs, i + 1,
+ attr_group = kvzalloc_struct(typeof(*attr_group), attrs, i + 1,
GFP_KERNEL);
...
- dev_dax = kvzalloc_struct(dev_dax, res, count, GFP_KERNEL);
+ dev_dax = kvzalloc_struct(struct dev_dax, res, count, GFP_KERNEL);
...
-#define kvzalloc_struct(p, member, n, gfp) \
- (typeof(p))kvzalloc_ab_c(n, \
- sizeof(*(p)->member) + __must_be_array((p)->member), \
- offsetof(typeof(*(p)), member), gfp)
+#define kvzalloc_struct(s, member, n, gfp) ({ \
+ s *__p; \
+ (s *)kvzalloc_ab_c(n, \
+ sizeof(*(__p)->member) + __must_be_array((__p)->member),\
+ offsetof(s, member), gfp); \
+})
Gives all the same checking as the current version, and doesn't involve
passing an uninitialised pointer to the macro.
It also looks pretty similar:
p = kvzalloc(sizeof(*p), GFP_KERNEL);
p = kvzalloc_struct(typeof(*p), array, count, GFP_KERNEL);
p = kvzalloc_array(sizeof(*p), count);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-15 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 20:11 [PATCH v2 0/8] Add kvzalloc_struct to complement kvzalloc_array Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 1/8] mm: Add kernel-doc for kvfree Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 2/8] mm: Add kvmalloc_ab_c and kvzalloc_struct Matthew Wilcox
2018-02-14 20:45 ` Joe Perches
2018-02-14 21:12 ` Matthew Wilcox
2018-02-14 21:24 ` Joe Perches
2018-02-14 21:27 ` Joe Perches
2018-02-14 21:29 ` Matthew Wilcox
2018-02-14 23:58 ` Andrew Morton
2018-02-15 3:40 ` Matthew Wilcox
2018-02-15 17:36 ` Matthew Wilcox [this message]
2018-02-14 20:11 ` [PATCH v2 3/8] Convert virtio_console to kvzalloc_struct Matthew Wilcox
2018-02-14 20:19 ` Joe Perches
2018-02-14 20:28 ` Matthew Wilcox
2018-02-14 20:30 ` Joe Perches
2018-02-14 20:11 ` [PATCH v2 4/8] Convert dax device " Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 5/8] Convert infiniband uverbs " Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 6/8] Convert v4l2 event " Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 7/8] Convert vhost " Matthew Wilcox
2018-02-14 20:11 ` [PATCH v2 8/8] Convert jffs2 acl " Matthew Wilcox
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=20180215173639.GA10146@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.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;
as well as URLs for NNTP newsgroup(s).