From: "Li,Rongqing" <lirongqing@baidu.com>
To: Yunsheng Lin <linyunsheng@huawei.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [PATCH 1/2][net-next] skbuff: move netlink_large_alloc_large_skb() to skbuff.c
Date: Thu, 2 Nov 2023 12:09:21 +0000 [thread overview]
Message-ID: <d8fe126e98d1494baddc715c39deef3d@baidu.com> (raw)
In-Reply-To: <50622ac2-0939-af35-5d62-c56249e7bd26@huawei.com>
> -----Original Message-----
> From: Yunsheng Lin <linyunsheng@huawei.com>
> Sent: Thursday, November 2, 2023 7:02 PM
> To: Li,Rongqing <lirongqing@baidu.com>; netdev@vger.kernel.org
> Subject: Re: [PATCH 1/2][net-next] skbuff: move netlink_large_alloc_large_skb()
> to skbuff.c
>
> On 2023/11/2 14:28, Li RongQing wrote:
> > move netlink_alloc_large_skb and netlink_skb_destructor to skbuff.c
> > and rename them more generic, so they can be used elsewhere large
> > non-contiguous physical memory is needed
> >
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > ---
> > include/linux/skbuff.h | 3 +++
> > net/core/skbuff.c | 40
> ++++++++++++++++++++++++++++++++++++++++
> > net/netlink/af_netlink.c | 41
> > ++---------------------------------------
> > 3 files changed, 45 insertions(+), 39 deletions(-)
> >
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h index
> > 4174c4b..774a401 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -5063,5 +5063,8 @@ static inline void skb_mark_for_recycle(struct
> > sk_buff *skb) ssize_t skb_splice_from_iter(struct sk_buff *skb, struct iov_iter
> *iter,
> > ssize_t maxsize, gfp_t gfp);
> >
> > +
> > +void large_skb_destructor(struct sk_buff *skb); struct sk_buff
> > +*alloc_large_skb(unsigned int size, int broadcast);
> > #endif /* __KERNEL__ */
> > #endif /* _LINUX_SKBUFF_H */
> > diff --git a/net/core/skbuff.c b/net/core/skbuff.c index
> > 4570705..20ffcd5 100644
> > --- a/net/core/skbuff.c
> > +++ b/net/core/skbuff.c
> > @@ -6917,3 +6917,43 @@ ssize_t skb_splice_from_iter(struct sk_buff *skb,
> struct iov_iter *iter,
> > return spliced ?: ret;
> > }
> > EXPORT_SYMBOL(skb_splice_from_iter);
> > +
> > +void large_skb_destructor(struct sk_buff *skb) {
> > + if (is_vmalloc_addr(skb->head)) {
> > + if (!skb->cloned ||
> > + !atomic_dec_return(&(skb_shinfo(skb)->dataref)))
> > + vfree(skb->head);
> > +
> > + skb->head = NULL;
>
> There seems to be an assumption that skb returned from
> netlink_alloc_large_skb() is not expecting the frag page for shinfo->frags*, as the
> above NULL setting will bypass most of the handling in skb_release_data(),then
> how can we ensure that the user is not breaking the assumption if we make it
> more generic?
>
How about to add WARN_ON(skb_shinfo(skb)-> nr_frags) to find this condition
-Li RongQing
>
next prev parent reply other threads:[~2023-11-02 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 6:28 [PATCH 1/2][net-next] skbuff: move netlink_large_alloc_large_skb() to skbuff.c Li RongQing
2023-11-02 6:28 ` [PATCH 2/2][net-next] rtnetlink: using alloc_large_skb in rtnl_getlink Li RongQing
2023-11-02 11:01 ` [PATCH 1/2][net-next] skbuff: move netlink_large_alloc_large_skb() to skbuff.c Yunsheng Lin
2023-11-02 12:09 ` Li,Rongqing [this message]
2023-11-03 3:50 ` Yunsheng Lin
2023-11-03 5:03 ` Li,Rongqing
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=d8fe126e98d1494baddc715c39deef3d@baidu.com \
--to=lirongqing@baidu.com \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.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