From: Suren Baghdasaryan <surenb@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, joro@8bytes.org, will@kernel.org,
trond.myklebust@hammerspace.com, anna@kernel.org, arnd@arndb.de,
herbert@gondor.apana.org.au, davem@davemloft.net,
jikos@kernel.org, benjamin.tissoires@redhat.com, tytso@mit.edu,
jack@suse.com, dennis@kernel.org, tj@kernel.org, cl@linux.com,
jakub@cloudflare.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
linux-arch@vger.kernel.org, linux-crypto@vger.kernel.org,
bpf@vger.kernel.org, linux-input@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
kent.overstreet@linux.dev
Subject: Re: [PATCH 1/1] mm: change inlined allocation helpers to account at the call site
Date: Thu, 4 Apr 2024 10:08:45 -0700 [thread overview]
Message-ID: <CAJuCfpHbTCwDERz+Hh+aLZzNdtSFKA+Q7sW-xzvmFmtyHCqROg@mail.gmail.com> (raw)
In-Reply-To: <Zg7dmp5VJkm1nLRM@casper.infradead.org>
On Thu, Apr 4, 2024 at 10:04 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Thu, Apr 04, 2024 at 09:54:04AM -0700, Suren Baghdasaryan wrote:
> > +++ b/include/linux/dma-fence-chain.h
> > @@ -86,10 +86,7 @@ dma_fence_chain_contained(struct dma_fence *fence)
> > *
> > * Returns a new struct dma_fence_chain object or NULL on failure.
> > */
> > -static inline struct dma_fence_chain *dma_fence_chain_alloc(void)
> > -{
> > - return kmalloc(sizeof(struct dma_fence_chain), GFP_KERNEL);
> > -};
> > +#define dma_fence_chain_alloc() kmalloc(sizeof(struct dma_fence_chain), GFP_KERNEL)
>
> You've removed some typesafety here. Before, if I wrote:
>
> struct page *page = dma_fence_chain_alloc();
>
> the compiler would warn me that I've done something stupid. Now it
> can't tell. Suggest perhaps:
>
> #define dma_fence_chain_alloc() \
> (struct dma_fence_chain *)kmalloc(sizeof(struct dma_fence_chain), \
> GFP_KERNEL)
>
> but maybe there's a better way of doing that. There are a few other
> occurrences of the same problem in this monster patch.
Got your point.
>
> > +++ b/include/linux/hid_bpf.h
> > @@ -149,10 +149,7 @@ static inline int hid_bpf_connect_device(struct hid_device *hdev) { return 0; }
> > static inline void hid_bpf_disconnect_device(struct hid_device *hdev) {}
> > static inline void hid_bpf_destroy_device(struct hid_device *hid) {}
> > static inline void hid_bpf_device_init(struct hid_device *hid) {}
> > -static inline u8 *call_hid_bpf_rdesc_fixup(struct hid_device *hdev, u8 *rdesc, unsigned int *size)
> > -{
> > - return kmemdup(rdesc, *size, GFP_KERNEL);
> > -}
> > +#define call_hid_bpf_rdesc_fixup(_hdev, _rdesc, _size) kmemdup(_rdesc, *(_size), GFP_KERNEL)
>
> here
>
> > -static inline handle_t *jbd2_alloc_handle(gfp_t gfp_flags)
> > -{
> > - return kmem_cache_zalloc(jbd2_handle_cache, gfp_flags);
> > -}
> > +#define jbd2_alloc_handle(_gfp_flags) kmem_cache_zalloc(jbd2_handle_cache, _gfp_flags)
>
> here
>
> > +++ b/include/linux/skmsg.h
> > @@ -410,11 +410,8 @@ void sk_psock_stop_verdict(struct sock *sk, struct sk_psock *psock);
> > int sk_psock_msg_verdict(struct sock *sk, struct sk_psock *psock,
> > struct sk_msg *msg);
> >
> > -static inline struct sk_psock_link *sk_psock_init_link(void)
> > -{
> > - return kzalloc(sizeof(struct sk_psock_link),
> > - GFP_ATOMIC | __GFP_NOWARN);
> > -}
> > +#define sk_psock_init_link() \
> > + kzalloc(sizeof(struct sk_psock_link), GFP_ATOMIC | __GFP_NOWARN)
>
> here
>
> ... I kind of gave up at this point. You'll want to audit for yourself
> anyway ;-)
Yes, I'll go over it and will make the required changes. Thanks for
looking into it!
Suren.
next prev parent reply other threads:[~2024-04-04 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 16:54 Suren Baghdasaryan
2024-04-04 17:04 ` Matthew Wilcox
2024-04-04 17:08 ` Suren Baghdasaryan [this message]
2024-04-04 22:17 ` Suren Baghdasaryan
2024-04-04 22:28 ` Kent Overstreet
2024-04-04 22:33 ` Matthew Wilcox
2024-04-04 22:38 ` Kent Overstreet
2024-04-04 22:41 ` Andrew Morton
2024-04-04 23:00 ` Kent Overstreet
2024-04-04 23:16 ` Suren Baghdasaryan
2024-04-05 9:53 ` Jan Kara
2024-04-05 13:47 ` Suren Baghdasaryan
2024-04-05 12:44 ` Matthew Wilcox
2024-04-05 13:53 ` Suren Baghdasaryan
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=CAJuCfpHbTCwDERz+Hh+aLZzNdtSFKA+Q7sW-xzvmFmtyHCqROg@mail.gmail.com \
--to=surenb@google.com \
--cc=acpica-devel@lists.linux.dev \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=arnd@arndb.de \
--cc=benjamin.tissoires@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=dennis@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=iamjoonsoo.kim@lge.com \
--cc=iommu@lists.linux.dev \
--cc=jack@suse.com \
--cc=jakub@cloudflare.com \
--cc=jikos@kernel.org \
--cc=joro@8bytes.org \
--cc=kent.overstreet@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=will@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