From: Daniel Borkmann <daniel@iogearbox.net>
To: "Björn Töpel" <bjorn.topel@gmail.com>,
ast@kernel.org, netdev@vger.kernel.org
Cc: "Björn Töpel" <bjorn.topel@intel.com>,
magnus.karlsson@intel.com, magnus.karlsson@gmail.com,
bpf@vger.kernel.org, u9012063@gmail.com
Subject: Re: [PATCH bpf 1/2] libbpf: fix invalid munmap call
Date: Mon, 6 May 2019 10:26:00 +0200 [thread overview]
Message-ID: <20aaa3f5-fd93-9773-ca8a-40809e9dc981@iogearbox.net> (raw)
In-Reply-To: <20190430124536.7734-2-bjorn.topel@gmail.com>
On 04/30/2019 02:45 PM, Björn Töpel wrote:
> From: Björn Töpel <bjorn.topel@intel.com>
>
> When unmapping the AF_XDP memory regions used for the rings, an
> invalid address was passed to the munmap() calls. Instead of passing
> the beginning of the memory region, the descriptor region was passed
> to munmap.
>
> When the userspace application tried to tear down an AF_XDP socket,
> the operation failed and the application would still have a reference
> to socket it wished to get rid of.
>
> Reported-by: William Tu <u9012063@gmail.com>
> Fixes: 1cad07884239 ("libbpf: add support for using AF_XDP sockets")
> Signed-off-by: Björn Töpel <bjorn.topel@intel.com>
[...]
> out_mmap_tx:
> if (tx)
> - munmap(xsk->tx,
> - off.tx.desc +
> + munmap(tx_map, off.tx.desc +
> xsk->config.tx_size * sizeof(struct xdp_desc));
> out_mmap_rx:
> if (rx)
> - munmap(xsk->rx,
> - off.rx.desc +
> + munmap(rx_map, off.rx.desc +
> xsk->config.rx_size * sizeof(struct xdp_desc));
> out_socket:
> if (--umem->refcount)
> @@ -684,10 +681,12 @@ int xsk_umem__delete(struct xsk_umem *umem)
> optlen = sizeof(off);
> err = getsockopt(umem->fd, SOL_XDP, XDP_MMAP_OFFSETS, &off, &optlen);
> if (!err) {
> - munmap(umem->fill->ring,
> - off.fr.desc + umem->config.fill_size * sizeof(__u64));
> - munmap(umem->comp->ring,
> - off.cr.desc + umem->config.comp_size * sizeof(__u64));
> + (void)munmap(umem->fill->ring - off.fr.desc,
> + off.fr.desc +
> + umem->config.fill_size * sizeof(__u64));
> + (void)munmap(umem->comp->ring - off.cr.desc,
> + off.cr.desc +
> + umem->config.comp_size * sizeof(__u64));
What's the rationale to cast to void here and other places (e.g. below)?
If there's no proper reason, then lets remove it. Given the patch has already
been applied, please send a follow up. Thanks.
> }
>
> close(umem->fd);
> @@ -698,6 +697,7 @@ int xsk_umem__delete(struct xsk_umem *umem)
>
> void xsk_socket__delete(struct xsk_socket *xsk)
> {
> + size_t desc_sz = sizeof(struct xdp_desc);
> struct xdp_mmap_offsets off;
> socklen_t optlen;
> int err;
> @@ -710,14 +710,17 @@ void xsk_socket__delete(struct xsk_socket *xsk)
> optlen = sizeof(off);
> err = getsockopt(xsk->fd, SOL_XDP, XDP_MMAP_OFFSETS, &off, &optlen);
> if (!err) {
> - if (xsk->rx)
> - munmap(xsk->rx->ring,
> - off.rx.desc +
> - xsk->config.rx_size * sizeof(struct xdp_desc));
> - if (xsk->tx)
> - munmap(xsk->tx->ring,
> - off.tx.desc +
> - xsk->config.tx_size * sizeof(struct xdp_desc));
> + if (xsk->rx) {
> + (void)munmap(xsk->rx->ring - off.rx.desc,
> + off.rx.desc +
> + xsk->config.rx_size * desc_sz);
> + }
> + if (xsk->tx) {
> + (void)munmap(xsk->tx->ring - off.tx.desc,
> + off.tx.desc +
> + xsk->config.tx_size * desc_sz);
> + }
> +
> }
>
> xsk->umem->refcount--;
>
next prev parent reply other threads:[~2019-05-06 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 12:45 [PATCH bpf 0/2] libbpf: fixes for AF_XDP teardown Björn Töpel
2019-04-30 12:45 ` [PATCH bpf 1/2] libbpf: fix invalid munmap call Björn Töpel
2019-05-01 3:36 ` William Tu
2019-05-06 8:26 ` Daniel Borkmann [this message]
2019-05-06 8:40 ` Björn Töpel
2019-05-06 9:01 ` Daniel Borkmann
2019-04-30 12:45 ` [PATCH bpf 2/2] libbpf: proper XSKMAP cleanup Björn Töpel
2019-05-01 3:34 ` William Tu
2019-04-30 15:38 ` [PATCH bpf 0/2] libbpf: fixes for AF_XDP teardown Jonathan Lemon
2019-05-05 6:30 ` Alexei Starovoitov
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=20aaa3f5-fd93-9773-ca8a-40809e9dc981@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.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