From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Chao Yu <chao@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: data: fix possible overflow in check_swap_activate()
Date: Mon, 11 Dec 2023 00:14:16 +0300 [thread overview]
Message-ID: <5769c4fa-3112-3582-00a0-2b17757d8cab@omp.ru> (raw)
In-Reply-To: <e2167506-2b0a-a0f5-c0e9-0e8b6139c69e@kernel.org>
Hello!
Sorry for replying a month later than I should -- I got distracted by the
other Svace reports... It took a significant part of the weekend to swap this
stuff back in... :-/
On 11/7/23 6:29 PM, Chao Yu wrote:
[...]
>> In check_swap_activate(), if the *while* loop exits early (0- or 1-page
>> long swap file), an overflow happens while calculating the value of the
>> span parameter as the lowest_pblock variable ends up being greater than
>> the highest_pblock variable. Let's set *span to 0 in this case...
>
> What do you think of returning -EINVAL for such case? I assume this is a
> corner case.
I don't know the code well enough but I got the impression that iff
we have a file containing a single page, we'd have one successful call
of add_swap_extent(). Am I missing something?
>> Found by Linux Verification Center (linuxtesting.org) with the SVACE static
>> analysis tool.
>>
>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>> ---
>> This patch is against the 'master' branch of Jaegeuk Kim's F2FS repo...
>>
>> fs/f2fs/data.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>> index 916e317ac925..342cb0d5056d 100644
>> --- a/fs/f2fs/data.c
>> +++ b/fs/f2fs/data.c
>> @@ -4047,7 +4047,10 @@ static int check_swap_activate(struct swap_info_struct *sis,
>> cur_lblock += nr_pblocks;
>> }
>> ret = nr_extents;
>> - *span = 1 + highest_pblock - lowest_pblock;
>> + if (lowest_pblock <= highest_pblock)
>
> if (unlikely(higest_pblock < lowest_pblock))
Well, Greg KH says we shouldn't use unlikely() unless we can prove
that it indeed improves things...
> return -EINVAL;
>
> *span = 1 + highest_pblock - lowest_pblock;
>
> Thanks,
>
>> + *span = 1 + highest_pblock - lowest_pblock;
>> + else
>> + *span = 0;
>> if (cur_lblock == 0)
>> cur_lblock = 1; /* force Empty message */
>> sis->max = cur_lblock;
MBR, Sergey
prev parent reply other threads:[~2023-12-10 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 20:20 Sergey Shtylyov
2023-11-07 15:29 ` Chao Yu
2023-12-10 21:14 ` Sergey Shtylyov [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=5769c4fa-3112-3582-00a0-2b17757d8cab@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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®