[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89i+tMOYBrdbPmZYP6LOd0q8h4FRZWCAbKL5u9_k4ce3pqg@mail.gmail.com>
Date: Tue, 27 Feb 2024 19:15:04 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "David S . Miller" <davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
eric.dumazet@...il.com, Zhengchao Shao <shaozhengchao@...wei.com>
Subject: Re: [PATCH net-next] netlink: use kvmalloc() in netlink_alloc_large_skb()
On Tue, Feb 27, 2024 at 6:52 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Sat, 24 Feb 2024 09:06:30 +0000 Eric Dumazet wrote:
> > struct sk_buff *netlink_alloc_large_skb(unsigned int size, int broadcast)
> > {
> > + size_t head_size = SKB_HEAD_ALIGN(size);
> > struct sk_buff *skb;
> > void *data;
> >
> > - if (size <= NLMSG_GOODSIZE || broadcast)
> > + if (head_size <= PAGE_SIZE || broadcast)
> > return alloc_skb(size, GFP_KERNEL);
> >
> > - size = SKB_DATA_ALIGN(size) +
> > - SKB_DATA_ALIGN(sizeof(struct skb_shared_info));
> > -
> > - data = vmalloc(size);
> > - if (data == NULL)
> > + data = kvmalloc(head_size, GFP_KERNEL);
> > + if (!data)
> > return NULL;
> >
> > - skb = __build_skb(data, size);
> > - if (skb == NULL)
> > - vfree(data);
> > - else
> > + skb = __build_skb(data, head_size);
>
> Is this going to work with KFENCE? Don't we need similar size
> adjustment logic as we have in __slab_build_skb() ?
Note that the 2nd argument of __build_skb() has not been changed by my patch.
SKB_HEAD_ALIGN(size) == SKB_DATA_ALIGN(size) +
SKB_DATA_ALIGN(sizeof(struct skb_shared_info));
I do not expect kfence being a problem here ?
Either data is vmalloc, and the patch is a no-op,
either it is kmalloc(), and __build_skb() does nothing special,
kfence magic already happened.
>
> > + if (!skb)
> > + kvfree(data);
Note that skb->head at this point must be equal to @data
> > + else if (is_vmalloc_addr(data))
> > skb->destructor = netlink_skb_destructor;
Powered by blists - more mailing lists