From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: mark.rutland@arm.com, netdev@vger.kernel.org, willemb@google.com,
peterpenkov96@gmail.com
Subject: Re: [PATCH net] tun: fix tun_napi_alloc_frags() frag allocator
Date: Fri, 16 Feb 2018 16:21:17 -0500 (EST) [thread overview]
Message-ID: <20180216.162117.1787932940366763800.davem@davemloft.net> (raw)
In-Reply-To: <1518734835.3715.209.camel@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 15 Feb 2018 14:47:15 -0800
> From: Eric Dumazet <edumazet@google.com>
>
> <Mark Rutland reported>
> While fuzzing arm64 v4.16-rc1 with Syzkaller, I've been hitting a
> misaligned atomic in __skb_clone:
>
> atomic_inc(&(skb_shinfo(skb)->dataref));
>
> where dataref doesn't have the required natural alignment, and the
> atomic operation faults. e.g. i often see it aligned to a single
> byte boundary rather than a four byte boundary.
>
> AFAICT, the skb_shared_info is misaligned at the instant it's
> allocated in __napi_alloc_skb() __napi_alloc_skb()
> </end of report>
>
> Problem is caused by tun_napi_alloc_frags() using
> napi_alloc_frag() with user provided seg sizes,
> leading to other users of this API getting unaligned
> page fragments.
>
> Since we would like to not necessarily add paddings or alignments to
> the frags that tun_napi_alloc_frags() attaches to the skb, switch to
> another page frag allocator.
>
> As a bonus skb_page_frag_refill() can use GFP_KERNEL allocations,
> meaning that we can not deplete memory reserves as easily.
>
> Fixes: 90e33d459407 ("tun: enable napi_gro_frags() for TUN/TAP driver")
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Reported-by: Mark Rutland <mark.rutland@arm.com>
> Tested-by: Mark Rutland <mark.rutland@arm.com>
Applied and queued up for -stable, thanks Eric.
prev parent reply other threads:[~2018-02-16 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:04 v4.16-rc1 misaligned atomics in skb__clone / __napi_alloc_skb Mark Rutland
2018-02-15 17:20 ` Eric Dumazet
2018-02-15 17:24 ` Eric Dumazet
2018-02-15 17:31 ` Mark Rutland
2018-02-15 17:43 ` Eric Dumazet
2018-02-15 17:57 ` Mark Rutland
2018-02-15 22:47 ` [PATCH net] tun: fix tun_napi_alloc_frags() frag allocator Eric Dumazet
2018-02-16 21:21 ` David Miller [this message]
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=20180216.162117.1787932940366763800.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=peterpenkov96@gmail.com \
--cc=willemb@google.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).