[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAG0ZtY4FYGvXyapfCO4JXnBTxL5JXnfyMqufsCga3RtnSn3y2g@mail.gmail.com>
Date: Wed, 3 Aug 2022 02:29:24 -0400
From: c b <cbulinaru@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, willemb@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH v4 1/2] net: tap: NULL pointer derefence in
dev_parse_header_protocol when skb->dev is null
I sent these two w.o. in-reply, hopefully it work. sorry about confusion
[PATCH v5 net] selftests: add few test cases for tap driver
[PATCH v5 net] net: tap: NULL pointer derefence in
dev_parse_header_protocol when skb->dev is null
On Wed, 3 Aug 2022 at 00:43, Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Wed, 3 Aug 2022 00:28:45 -0400 Cezar Bulinaru wrote:
> > Fixes a NULL pointer derefence bug triggered from tap driver.
> > When tap_get_user calls virtio_net_hdr_to_skb the skb->dev is null
> > (in tap.c skb->dev is set after the call to virtio_net_hdr_to_skb)
> > virtio_net_hdr_to_skb calls dev_parse_header_protocol which
> > needs skb->dev field to be valid.
>
> Could you repost these patches as a normal, standalone series, with
> no fancy in-reply-to? Put [PATCH net v5] as the subject prefix.
> Patchwork bot is unable to follow your creativity it seems.
Powered by blists - more mailing lists