From: Andrew Kanner <andrew.kanner@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: syzbot+f817490f5bd20541b90a@syzkaller.appspotmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
edumazet@google.com, brouer@redhat.com, kuba@kernel.org,
pabeni@redhat.com,
linux-kernel-mentees@lists.linuxfoundation.org,
davem@davemloft.net
Subject: Re: [PATCH 2/2] drivers: net: prevent tun_can_build_skb() to exceed xdp size limits
Date: Tue, 25 Jul 2023 13:49:24 +0300 [thread overview]
Message-ID: <64bfa8b7.190a0220.b6db7.53b7@mx.google.com> (raw)
In-Reply-To: <CACGkMEt+LW8FBNwcn6f0cBwTOuKy+ZPy3Smg6fJgo9OrCUAOjQ@mail.gmail.com>
On Tue, Jul 25, 2023 at 11:39:46AM +0800, Jason Wang wrote:
> On Tue, Jul 25, 2023 at 6:15 AM Andrew Kanner <andrew.kanner@gmail.com> wrote:
> >
> > Tested with syzkaller repro with reduced packet size. It was
> > discovered that XDP_PACKET_HEADROOM is not checked in
> > tun_can_build_skb(), although pad may be incremented in
> > tun_build_skb().
> >
> > Fixes: 7df13219d757 ("tun: reserve extra headroom only when XDP is set")
> > Link: https://syzkaller.appspot.com/text?tag=ReproC&x=12b2593ea80000
> > Signed-off-by: Andrew Kanner <andrew.kanner@gmail.com>
> > ---
> > drivers/net/tun.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> > index 18ccbbe9830a..cdf2bd85b383 100644
> > --- a/drivers/net/tun.c
> > +++ b/drivers/net/tun.c
> > @@ -1582,7 +1582,13 @@ static void tun_rx_batched(struct tun_struct *tun, struct tun_file *tfile,
> > static bool tun_can_build_skb(struct tun_struct *tun, struct tun_file *tfile,
> > int len, int noblock, bool zerocopy, int *skb_xdp)
> > {
> > - if (SKB_DATA_ALIGN(len + TUN_RX_PAD) +
> > + int pad = TUN_RX_PAD;
> > + struct bpf_prog *xdp_prog = rcu_dereference(tun->xdp_prog);
>
> This misses rcu read lock.
>
> I wonder if things could be simpler if we move the limit check from
> tun_can_build_skb() to tun_build_skb():
>
> rcu_read_lock();
> xdp_prog = rcu_dereference(tun->xdp_prog);
> if (xdp_prog)
> pad += XDP_PACKET_HEADROOM;
> buflen += SKB_DATA_ALIGN(len + pad);
> rcu_read_unlock();
>
> Thanks
>
Thanks, I missed the part with rcu read lock for some reason.
It's a good idea to move / reduce duplication. Let me think and try to
fix according to your comments, I will resend it as v2.
--
Andrew Kanner
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2023-07-25 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:13 [PATCH 1/2] drivers: net: use xdp only inside tun_build_skb() Andrew Kanner
2023-07-24 22:13 ` [PATCH 2/2] drivers: net: prevent tun_can_build_skb() to exceed xdp size limits Andrew Kanner
2023-07-25 3:39 ` Jason Wang
2023-07-25 10:49 ` Andrew Kanner [this message]
2023-07-25 3:28 ` [PATCH 1/2] drivers: net: use xdp only inside tun_build_skb() Jason Wang
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=64bfa8b7.190a0220.b6db7.53b7@mx.google.com \
--to=andrew.kanner@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+f817490f5bd20541b90a@syzkaller.appspotmail.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