From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: chien.yen@oracle.com, davem@davemloft.net,
rds-devel@oss.oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rds: Make rds_message_copy_from_user() return 0 on success.
Date: Thu, 5 Feb 2015 22:23:01 +0000 [thread overview]
Message-ID: <20150205222301.GU29656@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20150205220734.GC28883@oracle.com>
On Thu, Feb 05, 2015 at 05:07:34PM -0500, Sowmini Varadhan wrote:
> That was the one that git-bisect flagged for me.. I think this one
> had the iov_iter_init() in rds_sendmsg() itself?
No, it doesn't - it only touches recvmsg side of things.
> As I recall, this
> change was already refactoring rds_message_copy_from_user() (and was the
> earliest version that was broken when I tested it)?
>
> should it have been 'put iov_iter into msghdr'? I just wanted
> to make sure some innocent user would know how far back to go,
> if they wanted to not trip on this one.
Look at your own patch; it affects only sendmsg() path, as does
"rds: switch rds_message_copy_from_user() to iov_iter". In fact, the code
it fixes had been introduced in that commit. I agree that the bug is
there and I agree with your fix; the only problem I have is your interpretation
of bisect. "rds: switch ->inc_copy_to_user() to passing iov_iter" is
the last one *not* to have that particular breakage.
Seriously, reread both commits and your fix:
"rds: switch ->inc_copy_to_user() to passing iov_iter" - only recvmsg side
"rds: switch rds_message_copy_from_user() to iov_iter" - only sendmsg side
your fix to rds_message_copy_from_user() - only sendmsg side
next prev parent reply other threads:[~2015-02-05 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 20:20 [PATCH] rds: Make rds_message_copy_from_user() return 0 on success Sowmini Varadhan
2015-02-05 21:58 ` Al Viro
2015-02-05 22:07 ` Sowmini Varadhan
2015-02-05 22:23 ` Al Viro [this message]
2015-02-05 22:41 ` [PATCHv2] " Sowmini Varadhan
2015-02-08 6:42 ` David Miller
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=20150205222301.GU29656@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=chien.yen@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sowmini.varadhan@oracle.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.