From: Luis Henriques <lhenriques@suse.de>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: wip-msgr2
Date: Fri, 18 Dec 2020 16:45:35 +0000 [thread overview]
Message-ID: <87lfdv83m8.fsf@suse.de> (raw)
In-Reply-To: <CAOi1vP8D2em7QeZNn5h21UN8AF159ZqbwGxorP7sG2msQMJwYw@mail.gmail.com> (Ilya Dryomov's message of "Thu, 17 Dec 2020 18:25:17 +0100")
(Ups! Looks like this email never left my drafts maildir.)
Ilya Dryomov <idryomov@gmail.com> writes:
> On Thu, Dec 17, 2020 at 5:45 PM Luis Henriques <lhenriques@suse.de> wrote:
>>
>> Ilya Dryomov <idryomov@gmail.com> writes:
>> <snip>
>> >
>> > Ah, I disabled KASAN for some performance testing and didn't turn
>> > it back on. This doesn't actually corrupt any memory because the
>> > 96-byte object that gets allocated is big enough. In fact, the
>> > relevant code used to request 96 bytes independent of the connection
>> > mode until I changed it to follow the on-wire format more strictly.
>> >
>> > This frame is 68 bytes in plane mode and 96 bytes in secure mode
>> > but we are requesting 68 bytes in both modes. The following should
>> > fix it:
>> >
>> > diff --git a/net/ceph/messenger_v2.c b/net/ceph/messenger_v2.c
>> > index 5e38c847317b..11fd47b36fc8 100644
>> > --- a/net/ceph/messenger_v2.c
>> > +++ b/net/ceph/messenger_v2.c
>> > @@ -1333,7 +1333,8 @@ static int prepare_auth_signature(struct
>> > ceph_connection *con)
>> > void *buf;
>> > int ret;
>> >
>> > - buf = alloc_conn_buf(con, head_onwire_len(SHA256_DIGEST_SIZE, false));
>> > + buf = alloc_conn_buf(con, head_onwire_len(SHA256_DIGEST_SIZE,
>> > + con_secure(con)));
>> > if (!buf)
>> > return -ENOMEM;
>>
>> Looks like this fix didn't made it into your pull-request. Did it just
>> fell through the cracks, or is this fixed somewhere else on the code?
>
> No, it didn't, it's in the testing branch:
>
> https://github.com/ceph/ceph-client/commit/add7ad675cd1bdaf2751da1af9295fb43896da66
Cool, thanks for confirming. Just wanted to make sure ;-)
Cheers,
--
Luis
next prev parent reply other threads:[~2020-12-18 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 13:43 wip-msgr2 Ilya Dryomov
2020-12-14 15:55 ` wip-msgr2 Luis Henriques
2020-12-14 16:59 ` wip-msgr2 Ilya Dryomov
2020-12-14 17:26 ` wip-msgr2 Luis Henriques
2020-12-15 13:14 ` wip-msgr2 Luis Henriques
2020-12-15 15:30 ` wip-msgr2 Ilya Dryomov
2020-12-15 16:14 ` wip-msgr2 Luis Henriques
2020-12-17 16:46 ` wip-msgr2 Luis Henriques
2020-12-17 17:25 ` wip-msgr2 Ilya Dryomov
2020-12-18 16:45 ` Luis Henriques [this message]
2020-12-16 15:31 ` wip-msgr2 Jeff Layton
2020-12-16 17:18 ` wip-msgr2 Ilya Dryomov
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=87lfdv83m8.fsf@suse.de \
--to=lhenriques@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox