From: David Miller <davem@davemloft.net>
To: joe.korty@ccur.com
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix kfree bug in sendmsg and recvmsg
Date: Wed, 17 Feb 2016 13:29:23 -0500 (EST) [thread overview]
Message-ID: <20160217.132923.1768889532497422907.davem@davemloft.net> (raw)
In-Reply-To: <20160217163805.GA15781@zipoli.ccur.com>
From: Joe Korty <joe.korty@ccur.com>
Date: Wed, 17 Feb 2016 11:38:05 -0500
> Fix kfree bug in recvmsg and sendmsg.
>
> We cannot kfree(iov) when iov points to an array on the
> stack, as that has the potential of corrupting memory.
>
> So re-introduce the if-stmt that used to protect kfree
> from this condition, code that was removed as part of
> a larger set of changes made by git commit da184284.
>
> Signed-off-by: Joe Korty <joe.korty@ccur.com>
Please submit networking patches to netdev@vger.kernel.org, thank you.
prev parent reply other threads:[~2016-02-17 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 16:38 [PATCH] Fix kfree bug in sendmsg and recvmsg Joe Korty
2016-02-17 16:44 ` Al Viro
2016-02-17 16:52 ` Al Viro
2016-02-17 18:29 ` David Miller [this message]
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=20160217.132923.1768889532497422907.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).