From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net 0/3] skb frag: kmap_atomic fixes
Date: Fri, 8 Jan 2021 12:11:49 -0500 [thread overview]
Message-ID: <20210108171152.2961251-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
skb frags may be backed by highmem and/or compound pages. Various
code calls kmap_atomic to safely access highmem pages. But this
needs additional care for compound pages. Fix a few issues:
patch 1 expect kmap mappings with CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP
patch 2 fixes kmap_atomic + compound page support in skb_seq_read
patch 3 fixes kmap_atomic + compound page support in esp
Willem de Bruijn (3):
net: support kmap_local forced debugging in skb_frag_foreach
net: compound page support in skb_seq_read
esp: avoid unneeded kmap_atomic call
include/linux/skbuff.h | 3 ++-
net/core/skbuff.c | 28 +++++++++++++++++++++++-----
net/ipv4/esp4.c | 7 +------
net/ipv6/esp6.c | 7 +------
4 files changed, 27 insertions(+), 18 deletions(-)
--
2.30.0.284.gd98b1dd5eaa7-goog
next reply other threads:[~2021-01-08 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 17:11 Willem de Bruijn [this message]
2021-01-08 17:11 ` [PATCH net 1/3] net: support kmap_local forced debugging in skb_frag_foreach Willem de Bruijn
2021-01-08 17:11 ` [PATCH net 2/3] net: compound page support in skb_seq_read Willem de Bruijn
2021-01-08 23:30 ` Willem de Bruijn
2021-01-09 22:09 ` Willem de Bruijn
2021-01-08 17:11 ` [PATCH net 3/3] esp: avoid unneeded kmap_atomic call Willem de Bruijn
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=20210108171152.2961251-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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).