From: Luis Henriques <luis.henriques@linux.dev>
To: Xiubo Li <xiubli@redhat.com>
Cc: Luis Henriques <luis.henriques@linux.dev>,
alex.markuze@ibm.com, Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2] ceph: ceph: fix out-of-bound array access when doing a file read
Date: Tue, 05 Nov 2024 09:21:59 +0000 [thread overview]
Message-ID: <87y11yavd4.fsf@camandro.org> (raw)
In-Reply-To: <7fffefc1-370d-4f04-979f-caeede1e9c0f@redhat.com> (Xiubo Li's message of "Tue, 5 Nov 2024 09:10:25 +0800")
Hi Xiubo!
On Tue, Nov 05 2024, Xiubo Li wrote:
> CC Alex
>
> Hi Luis,
>
> Alex will take over it and help push it recently. I am a bit busy with my new
> things these days.
Thanks a lot. I think the difficult bit to understand (for me, at least!)
are any MDS side-effects, as you earlier mentioned the filelocking
semantics. I'm not sure if/how this patch may cause troubles there.
> BTW, if possible please join 'ceph' workspace's #cephfs slack channel and you
> could push it faster there ?
I believe that channel is bridged to IRC (OFTC network), where I'm already
lurking (nick 'henrix'). And I see you have already ping'ed others there.
However, I'm currently on PTO, so my replies there may be asynchronous :-)
Cheers,
--
Luís
>
> Thanks
>
> - Xiubo
>
>
> 在 2024/11/4 22:34, Luis Henriques 写道:
>> Hi Xiubo, Hi Ilya,
>>
>> On Mon, Sep 30 2024, Luis Henriques wrote:
>> [...]
>>> Hi Xiubo,
>>>
>>> I know you've been busy, but I was wondering if you (or someone else) had
>>> a chance to have a look at this. It's pretty easy to reproduce, and it
>>> has been seen in production. Any chances of getting some more feedback on
>>> this fix?
>> It has been a while since I first reported this issue. Taking the risk of
>> being "that annoying guy", I'd like to ping you again on this. I've
>> managed to reproduce the issue very easily, and it's also being triggered
>> very frequently in production. Any news?
>>
>> Cheers,
next prev parent reply other threads:[~2024-11-05 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 13:57 [RFC PATCH v2] ceph: ceph: fix out-of-bound array access when doing a file read Luis Henriques (SUSE)
2024-09-06 11:17 ` Xiubo Li
2024-09-06 11:30 ` Luis Henriques
2024-09-06 12:48 ` Xiubo Li
2024-09-30 15:30 ` Luis Henriques
2024-11-04 14:34 ` Luis Henriques
2024-11-05 1:10 ` Xiubo Li
2024-11-05 9:21 ` Luis Henriques [this message]
2024-11-06 20:40 ` Goldwyn Rodrigues
2024-11-07 11:09 ` Luis Henriques
2024-11-27 13:47 ` Alex Markuze
2024-11-28 17:42 ` Luis Henriques
2024-11-28 18:19 ` Alex Markuze
2024-11-28 18:52 ` Luis Henriques
2024-11-28 19:09 ` Alex Markuze
2024-11-28 19:31 ` Alex Markuze
2024-12-11 10:36 ` Alex Markuze
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=87y11yavd4.fsf@camandro.org \
--to=luis.henriques@linux.dev \
--cc=alex.markuze@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@redhat.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