From: Luis Henriques <luis.henriques@linux.dev>
To: Xiubo Li <xiubli@redhat.com>
Cc: Ilya Dryomov <idryomov@gmail.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ceph: fix out-of-bound array access when doing a file read
Date: Fri, 23 Aug 2024 08:25:20 +0100 [thread overview]
Message-ID: <87ikvrhfa7.fsf@linux.dev> (raw)
In-Reply-To: <0205e0b6-fad9-4519-adec-f1d1b30d9ef9@redhat.com> (Xiubo Li's message of "Fri, 23 Aug 2024 09:48:16 +0800")
On Fri, Aug 23 2024, Xiubo Li wrote:
> On 8/22/24 23:01, Luis Henriques (SUSE) wrote:
>> If, while doing a read, the inode is updated and the size is set to zero,
>> __ceph_sync_read() may not be able to handle it. It is thus easy to hit a
>> NULL pointer dereferrence by continuously reading a file while, on another
>> client, we keep truncating and writing new data into it.
>>
>> This patch fixes the issue by adding extra checks to avoid integer overflows
>> for the case of a zero size inode. This will prevent the loop doing page
>> copies from running and thus accessing the pages[] array beyond num_pages.
>>
>> Link: https://tracker.ceph.com/issues/67524
>> Signed-off-by: Luis Henriques (SUSE) <luis.henriques@linux.dev>
>> ---
>> Hi!
>>
>> Please note that this patch is only lightly tested and, to be honest, I'm
>> not sure if this is the correct way to fix this bug. For example, if the
>> inode size is 0, then maybe ceph_osdc_wait_request() should have returned
>> 0 and the problem would be solved. However, it seems to be returning the
>> size of the reply message and that's not something easy to change. Or maybe
>> I'm just reading it wrong. Anyway, this is just an RFC to see if there's
>> other ideas.
>>
>> Also, the tracker contains a simple testcase for crashing the client.
>>
>> fs/ceph/file.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ceph/file.c b/fs/ceph/file.c
>> index 4b8d59ebda00..dc23d5e5b11e 100644
>> --- a/fs/ceph/file.c
>> +++ b/fs/ceph/file.c
>> @@ -1200,9 +1200,9 @@ ssize_t __ceph_sync_read(struct inode *inode, loff_t *ki_pos,
>> }
>> idx = 0;
>> - if (ret <= 0)
>> + if ((ret <= 0) || (i_size == 0))
>
> Hi Luis,
>
> This change looks incorrect to me.
>
> As I mentioned before when the 'IFILE' lock is in MIX state the 'Frw' caps could
> be issued to multiple clients at the same time. Which means the file could be
> updated by another client and the local 'i_size' may haven't been changed in
> time. So in this case the 'ret' will be larger than '0' and the 'i_size' could
> be '0'.
>
>
>> left = 0;
>> - else if (off + ret > i_size)
>> + else if ((i_size >= off) && (off + ret > i_size))
>
> And the 'off' also could equal to little than the 'i_size'.
>
> BTW, could you reproduce the crash issue ?
Yes, 100% reproducible :-)
See https://tracker.ceph.com/issues/67524
Cheers,
--
Luís
>
> Thanks
>
> - Xiubo
>
>> left = i_size - off;
>> else
>> left = ret;
>> @@ -1210,6 +1210,7 @@ ssize_t __ceph_sync_read(struct inode *inode, loff_t *ki_pos,
>> size_t plen, copied;
>> plen = min_t(size_t, left, PAGE_SIZE - page_off);
>> + WARN_ON_ONCE(idx >= num_pages);
>> SetPageUptodate(pages[idx]);
>> copied = copy_page_to_iter(pages[idx++],
>> page_off, plen, to);
>> @@ -1234,7 +1235,7 @@ ssize_t __ceph_sync_read(struct inode *inode, loff_t *ki_pos,
>> }
>> if (ret > 0) {
>> - if (off >= i_size) {
>> + if ((i_size >= *ki_pos) && (off >= i_size)) {
>> *retry_op = CHECK_EOF;
>> ret = i_size - *ki_pos;
>> *ki_pos = i_size;
>>
>
next prev parent reply other threads:[~2024-08-23 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 15:01 [RFC PATCH] ceph: fix out-of-bound array access when doing a file read Luis Henriques (SUSE)
2024-08-23 1:48 ` Xiubo Li
2024-08-23 7:25 ` Luis Henriques [this message]
2024-08-25 23:53 ` Xiubo Li
2024-08-23 10:33 ` Luis Henriques
2024-08-27 13:36 ` Luis Henriques
2024-08-28 5:47 ` Xiubo Li
2024-08-28 15:48 ` Luis Henriques
2024-09-06 11:08 ` Xiubo Li
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=87ikvrhfa7.fsf@linux.dev \
--to=luis.henriques@linux.dev \
--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 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.