On 10/5/2020 7:48 AM, Vladimir Oltean wrote:
> Currently skb_dump has a restriction to only dump full packet for the
> first 5 socket buffers, then only headers will be printed. Remove this
> arbitrary and confusing restriction, which is only documented vaguely
> ("up to") in the comments above the prototype.
>
So, this limitation appeared very clearly in the original commit,
6413139dfc64 ("skbuff: increase verbosity when dumping skb data")..
Searching the netdev list, that patch links back to this one as the
original idea:
https://patchwork.ozlabs.org/project/netdev/patch/20181121021309.6595-2-xiyou.wangc...@gmail.com/
I can't find any further justification on that limit. I suppose the
primary reasoning being if you somehow call this function in a loop this
would avoid dumping the entire packet over and over?
Thanks,
Jake
> Signed-off-by: Vladimir Oltean <vladimir.olt...@nxp.com>
> ---
> net/core/skbuff.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index e0774471f56d..720076a6e2b1 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -712,11 +712,10 @@ EXPORT_SYMBOL(kfree_skb_list);
> *
> * Must only be called from net_ratelimit()-ed paths.
> *
> - * Dumps up to can_dump_full whole packets if full_pkt, headers otherwise.
> + * Dumps whole packets if full_pkt, only headers otherwise.
> */
> void skb_dump(const char *level, const struct sk_buff *skb, bool full_pkt)
> {
> - static atomic_t can_dump_full = ATOMIC_INIT(5);
> struct skb_shared_info *sh = skb_shinfo(skb);
> struct net_device *dev = skb->dev;
> struct sock *sk = skb->sk;
> @@ -725,9 +724,6 @@ void skb_dump(const char *level, const struct sk_buff
> *skb, bool full_pkt)
> int headroom, tailroom;
> int i, len, seg_len;
>
> - if (full_pkt)
> - full_pkt = atomic_dec_if_positive(&can_dump_full) >= 0;
> -
> if (full_pkt)
> len = skb->len;
> else
>
