On Fr, 2014-07-25 at 16:52 -0400, Sasha Levin wrote:
> On 07/25/2014 11:23 AM, Andrey Ryabinin wrote:
> > After this report there was no usual "Unable to handle kernel NULL pointer
> > dereference"
> > and this gave me a clue that address 0 is mapped and contains valid socket
> > address structure in it.
>
> Interesting. Does it mean that all network protocols that check it for being
> NULL instead of checking
> the length are incorrect?
I would not like to go down this route and keep msg->msg_namelen and
msg->msg_name in sync after verify_iovec.
> (such as:)
>
> if (msg->msg_name) {
> DECLARE_SOCKADDR(struct sockaddr_can *, addr, msg->msg_name);
>
> [...]
>
Thanks,
Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
