From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Vitaliy Shevtsov <v.shevtsov@maxima.ru>,
lvc-project@linuxtesting.org, Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [lvc-project] [PATCH] IB/hfi1: fix buffer underflow in fault injection code
Date: Wed, 15 Jan 2025 23:16:18 -0500 [thread overview]
Message-ID: <3a3a857e-7769-40b4-81d2-2a4e71bd301f@cornelisnetworks.com> (raw)
In-Reply-To: <gwdzoxk5gq5ve5jqklt4mkuoo25nhpjagjwbjuqvcrwhccauet@2frrkt22grg7>
On 1/15/25 2:14 PM, Fedor Pchelkin wrote:
> On Wed, 15. Jan 12:55, Dennis Dalessandro wrote:
>> On 12/27/24 6:09 PM, Vitaliy Shevtsov wrote:
>>> [Why]
>>> The fault injection code may have a buffer underflow, which may cause
>>> memory corruption by writing a newline character before the base address of
>>> the array. This can happen if the fault->opcodes bitmap is empty.
>>>
>>> Since a file in debugfs is created with an empty bitmap, it is possible to
>>> read the file before any set bits are written to it.
>>>
>>> [How]
>>> Fix this by checking that the size variable is greater than zero, otherwise
>>> return zero as the number of bytes read.
>>>
>>> Found by Linux Verification Center (linuxtesting.org) with Svace.
>>>
>>> Fixes: a74d5307caba ("IB/hfi1: Rework fault injection machinery")
>>> Signed-off-by: Vitaliy Shevtsov <v.shevtsov@maxima.ru>
>>> ---
>>> drivers/infiniband/hw/hfi1/fault.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/infiniband/hw/hfi1/fault.c b/drivers/infiniband/hw/hfi1/fault.c
>>> index ec9ee59fcf0c..2d87f9c8b89d 100644
>>> --- a/drivers/infiniband/hw/hfi1/fault.c
>>> +++ b/drivers/infiniband/hw/hfi1/fault.c
>>> @@ -190,7 +190,8 @@ static ssize_t fault_opcodes_read(struct file *file, char __user *buf,
>>> bit = find_next_bit(fault->opcodes, bitsize, zero);
>>> }
>>> debugfs_file_put(file->f_path.dentry);
>>> - data[size - 1] = '\n';
>>> + if (size)
>>> + data[size - 1] = '\n';
>>> data[size] = '\0';
>>> ret = simple_read_from_buffer(buf, len, pos, data, size);
>>> free_data:
>>
>> I don't think size can ever be 0. No reason to change this I don't think.
>>
>> -Denny
>>
>
> Seems the patch description rather clearly shows the size can be zero in
> case the corresponding opcodes bitmap is empty. Which is the case when
> user reads the file before writing anything to it.
Guess it's OK then.
Acked-by: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
prev parent reply other threads:[~2025-01-16 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 23:09 Vitaliy Shevtsov
2025-01-15 17:55 ` Dennis Dalessandro
2025-01-15 19:14 ` [lvc-project] " Fedor Pchelkin
2025-01-16 4:16 ` Dennis Dalessandro [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=3a3a857e-7769-40b4-81d2-2a4e71bd301f@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=v.shevtsov@maxima.ru \
/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
all inboxes | Powered by JetHome®