Re: [PATCH v2] net: tap: NULL pointer derefence in dev_parse_header_protocol... | netdev

(off-list ancestor, not in this archive)
(no subject) · Cezar Bulinaru <hidden> · 2022-07-29
[PATCH v2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · Cezar Bulinaru <hidden> · 2022-07-29
Re: [PATCH v2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · Willem de Bruijn <willemdebruijn.kernel@gmail.com> · 2022-07-29
Re: [PATCH v2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · Jakub Kicinski <kuba@kernel.org> · 2022-07-30
[PATCH v3 1/2] Fixes: 924a9bc362a5 ("net: check if protocol extracted by virtio_net_hdr_set_proto is correct") · Cezar Bulinaru <hidden> · 2022-08-01
[PATCH v3 2/2] selftests: add few test cases for tap driver · Cezar Bulinaru <hidden> · 2022-08-01
Re: [PATCH v3 2/2] selftests: add few test cases for tap driver · Willem de Bruijn <willemdebruijn.kernel@gmail.com> · 2022-08-01
[PATCH v4 2/2] selftests: add few test cases for tap driver · Cezar Bulinaru <hidden> · 2022-08-03
Re: [PATCH v3 1/2] Fixes: 924a9bc362a5 ("net: check if protocol extracted by virtio_net_hdr_set_proto is correct") · Willem de Bruijn <willemdebruijn.kernel@gmail.com> · 2022-08-01
[PATCH v4 1/2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · Cezar Bulinaru <hidden> · 2022-08-03
Re: [PATCH v4 1/2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · Jakub Kicinski <kuba@kernel.org> · 2022-08-03
Re: [PATCH v4 1/2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null · c b <hidden> · 2022-08-03

Re: [PATCH v2] net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null

From: Jakub Kicinski <kuba@kernel.org>
Date: 2022-07-30 02:03:17

On Fri, 29 Jul 2022 08:52:04 +0200 Willem de Bruijn wrote:

quoted

 drivers/net/tap.c                    |  21 +-
 tools/testing/selftests/net/Makefile |   2 +-
 tools/testing/selftests/net/tap.c    | 395 +++++++++++++++++++++++++++

Is there prior art in mixing fixes and tests? Should the test go to
net or always to net-next?

Not sure if there is any official guidance, but I usually put both 
together. Separate patches in the same series, targeting one tree.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help