From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Ilya Dryomov <idryomov@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.9] libceph: fix CEPH_FEATURE_CEPHX_V2 check in calc_signature()
Date: Wed, 09 Jan 2019 16:28:47 +0000 [thread overview]
Message-ID: <1547051327.3229.3.camel@codethink.co.uk> (raw)
In-Reply-To: <20190109141709.4921-1-idryomov@gmail.com>
On Wed, 2019-01-09 at 15:17 +0100, Ilya Dryomov wrote:
> Upstream commit cc255c76c70f ("libceph: implement CEPHX_V2 calculation
> mode") was adjusted incorrectly: CEPH_FEATURE_CEPHX_V2 if condition got
> inverted, thus breaking 4.9.144 and later kernels for all setups that
> use cephx.
Whoa, sorry about that.
Ben.
> Cc: Ben Hutchings <ben.hutchings@codethink.co.uk>
> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
> ---
> net/ceph/auth_x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ceph/auth_x.c b/net/ceph/auth_x.c
> index 29e23b5cb2ed..a4896e4a1c9a 100644
> --- a/net/ceph/auth_x.c
> +++ b/net/ceph/auth_x.c
> @@ -804,7 +804,7 @@ static int calc_signature(struct ceph_x_authorizer *au, struct ceph_msg *msg,
> void *enc_buf = au->enc_buf;
> int ret;
>
> - if (msg->con->peer_features & CEPH_FEATURE_CEPHX_V2) {
> + if (!(msg->con->peer_features & CEPH_FEATURE_CEPHX_V2)) {
> struct {
> __le32 len;
> __le32 header_crc;
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
prev parent reply other threads:[~2019-01-09 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 14:17 [PATCH 4.9] libceph: fix CEPH_FEATURE_CEPHX_V2 check in calc_signature() Ilya Dryomov
2019-01-09 16:28 ` Ben Hutchings [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=1547051327.3229.3.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=idryomov@gmail.com \
--cc=stable@vger.kernel.org \
/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.