From: Jakub Kicinski <kuba@kernel.org>
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, kuniyu@amazon.com, dh.herrmann@gmail.com,
jhs@mojatatu.com
Subject: Re: [PATCH net] net/netlink: fix NETLINK_LIST_MEMBERSHIPS group array length check
Date: Fri, 26 May 2023 20:33:01 -0700 [thread overview]
Message-ID: <20230526203301.6933b4b3@kernel.org> (raw)
In-Reply-To: <20230525144609.503744-1-pctammela@mojatatu.com>
On Thu, 25 May 2023 11:46:09 -0300 Pedro Tammela wrote:
> For the socket option 'NETLINK_LIST_MEMBERSHIPS' the length is defined
> as the number of u32 required to represent the whole bitset.
I don't think it is, it's a getsockopt() len is in bytes.
> User space then usually queries the required size and issues a subsequent
> getsockopt call with the correct parameters[1].
>
> The current code has an unit mismatch between 'len' and 'pos', where
> 'len' is the number of u32 in the passed array while 'pos' is the
> number of bytes iterated in the groups bitset.
> For netlink groups greater than 32, which from a quick glance
> is a rare occasion, the mismatch causes the misreport of groups e.g.
> if a rtnl socket is a member of group 34, it's reported as not a member
> (all 0s).
IDK... I haven't tried to repro but looking at the code the more
suspicious line of code is this one:
if (put_user(ALIGN(nlk->ngroups / 8, sizeof(u32)), optlen))
It's going to round down bytes, and I don't think it's intending to.
It should be DIV_ROUND_UP(, 8) then ALIGN(, 4) right?
--
pw-bot: cr
next prev parent reply other threads:[~2023-05-27 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 14:46 [PATCH net] net/netlink: fix NETLINK_LIST_MEMBERSHIPS group array length check Pedro Tammela
2023-05-26 9:26 ` Simon Horman
2023-05-27 3:33 ` Jakub Kicinski [this message]
2023-05-27 15:01 ` Pedro Tammela
2023-05-29 6:40 ` Jakub Kicinski
2023-05-29 14:37 ` Pedro Tammela
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=20230526203301.6933b4b3@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dh.herrmann@gmail.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.