public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Shchirskyi <oleksandr.shchirskyi@linux.intel.com>
To: Song Liu <song@kernel.org>, Xiao Ni <xni@redhat.com>
Cc: Nigel Croxon <ncroxon@redhat.com>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [PATCH 1/1] It needs to check offset array is NULL or not in async_xor_offs
Date: Tue, 1 Jun 2021 18:34:20 +0200	[thread overview]
Message-ID: <9bb16539-d084-c2ba-256b-bc0901bccf7d@linux.intel.com> (raw)
In-Reply-To: <CAPhsuW5O0ii77JFpYTB+RyPKzHmqQDGdr+8wMC4=CNtv=_daNg@mail.gmail.com>

On 6/1/2021 12:53 AM, Song Liu wrote:
> On Thu, May 27, 2021 at 11:16 PM Xiao Ni <xni@redhat.com> wrote:
>>
>> Now we support sharing one big page when PAGE_SIZE is not equal 4096.
>> 4096 bytes is the default stripe size. To support this it adds a
>> page offset array in raid5_percpu's scribble. It passes the page
>> offset array to async_xor_offs. But there are some users that don't
>> use the page offset array. In raid5-ppl.c, async_xor passes NULL to
>> asynx_xor_offs. So it needs to check src_offs is NULL or not.
>>
>> Fixes: ceaf2966ab08(async_xor: increase src_offs when dropping destination page)
>> Reported-by: Oleksandr Shchirskyi <oleksandr.shchirskyi@linux.intel.com>
>> Signed-off-by: Xiao Ni <xni@redhat.com>
> 
> Oleksandr,
> 
> Could you please verify this fixes the issue, and reply with your Tested-by?
> 
> Thanks,
> Song
> 

I can confirm that this patch fixes a NULL pointer dereference issue for me.
Thanks for the fix!

Tested-by: Oleksandr Shchirskyi <oleksandr.shchirskyi@intel.com>

>> ---
>>   crypto/async_tx/async_xor.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/crypto/async_tx/async_xor.c b/crypto/async_tx/async_xor.c
>> index 6cd7f70..d8a9152 100644
>> --- a/crypto/async_tx/async_xor.c
>> +++ b/crypto/async_tx/async_xor.c
>> @@ -233,7 +233,8 @@ async_xor_offs(struct page *dest, unsigned int offset,
>>                  if (submit->flags & ASYNC_TX_XOR_DROP_DST) {
>>                          src_cnt--;
>>                          src_list++;
>> -                       src_offs++;
>> +                       if (src_offs)
>> +                               src_offs++;
>>                  }
>>
>>                  /* wait for any prerequisite operations */
>> --
>> 2.7.5
>>


Regards,
Oleksandr Shchirskyi

      reply	other threads:[~2021-06-01 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28  6:16 [PATCH 1/1] It needs to check offset array is NULL or not in async_xor_offs Xiao Ni
2021-05-31 22:53 ` Song Liu
2021-06-01 16:34   ` Oleksandr Shchirskyi [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=9bb16539-d084-c2ba-256b-bc0901bccf7d@linux.intel.com \
    --to=oleksandr.shchirskyi@linux.intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=ncroxon@redhat.com \
    --cc=song@kernel.org \
    --cc=xni@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