public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Naohiro Aota <naohiro.aota@wdc.com>,
	Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] btrfs: fix extent buffer read/write range checks
Date: Fri, 26 Jul 2019 14:36:10 +0800	[thread overview]
Message-ID: <71f0399e-0719-ca8c-cb7b-aba5de5d0c5a@gmx.com> (raw)
In-Reply-To: <20190726061300.gvwypjd32elqtkhu@naota.dhcp.fujisawa.hgst.com>



On 2019/7/26 下午2:13, Naohiro Aota wrote:
> On Fri, Jul 26, 2019 at 08:38:27AM +0300, Nikolay Borisov wrote:
>>
>>
>> On 26.07.19 г. 8:27 ч., Naohiro Aota wrote:
>>> Several functions to read/write an extent buffer check if specified
>>> offset
>>> range resides in the size of the extent buffer. However, those checks
>>> have
>>> two problems:
>>>
>>> (1) they don't catch "start == eb->len" case.
>>> (2) it checks offset in extent buffer against logical address using
>>>     eb->start.
>>>
>>> Generally, eb->start is much larger than the offset, so the second
>>> WARN_ON
>>> was almost useless.
>>>
>>> Fix these problems in read_extent_buffer_to_user(),
>>> {memcmp,write,memzero}_extent_buffer().
>>>
>>> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
>>
>> Qu already sent similar patch:
>>
>> [PATCH v2 1/5] btrfs: extent_io: Do extra check for extent buffer read
>> write functions
>>
>>
>> He centralised the checking code, your >= fixes though should be merged
>> there.
>
> Oops, I missed that series. Thank you for pointing out. Then, this
> should be merged into Qu's version.
>
> Qu, could you pick the change from "start > eb->len" to "start >= eb->len"?

start >= eb->len is not always invalid.

start == eb->len while len == 0 is still valid.

Or should we also warn such bad practice?

Thanks,
Qu

>
>>
>>
>>> ---
>>>  fs/btrfs/extent_io.c | 16 ++++++++--------
>>>  1 file changed, 8 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
>>> index 50cbaf1dad5b..c0174f530568 100644
>>> --- a/fs/btrfs/extent_io.c
>>> +++ b/fs/btrfs/extent_io.c
>>> @@ -5545,8 +5545,8 @@ int read_extent_buffer_to_user(const struct
>>> extent_buffer *eb,
>>>      unsigned long i = (start_offset + start) >> PAGE_SHIFT;
>>>      int ret = 0;
>>>
>>> -    WARN_ON(start > eb->len);
>>> -    WARN_ON(start + len > eb->start + eb->len);
>>> +    WARN_ON(start >= eb->len);
>>> +    WARN_ON(start + len > eb->len);
>>>
>>>      offset = offset_in_page(start_offset + start);
>>>
>>> @@ -5623,8 +5623,8 @@ int memcmp_extent_buffer(const struct
>>> extent_buffer *eb, const void *ptrv,
>>>      unsigned long i = (start_offset + start) >> PAGE_SHIFT;
>>>      int ret = 0;
>>>
>>> -    WARN_ON(start > eb->len);
>>> -    WARN_ON(start + len > eb->start + eb->len);
>>> +    WARN_ON(start >= eb->len);
>>> +    WARN_ON(start + len > eb->len);
>>>
>>>      offset = offset_in_page(start_offset + start);
>>>
>>> @@ -5678,8 +5678,8 @@ void write_extent_buffer(struct extent_buffer
>>> *eb, const void *srcv,
>>>      size_t start_offset = offset_in_page(eb->start);
>>>      unsigned long i = (start_offset + start) >> PAGE_SHIFT;
>>>
>>> -    WARN_ON(start > eb->len);
>>> -    WARN_ON(start + len > eb->start + eb->len);
>>> +    WARN_ON(start >= eb->len);
>>> +    WARN_ON(start + len > eb->len);
>>>
>>>      offset = offset_in_page(start_offset + start);
>>>
>>> @@ -5708,8 +5708,8 @@ void memzero_extent_buffer(struct extent_buffer
>>> *eb, unsigned long start,
>>>      size_t start_offset = offset_in_page(eb->start);
>>>      unsigned long i = (start_offset + start) >> PAGE_SHIFT;
>>>
>>> -    WARN_ON(start > eb->len);
>>> -    WARN_ON(start + len > eb->start + eb->len);
>>> +    WARN_ON(start >= eb->len);
>>> +    WARN_ON(start + len > eb->len);
>>>
>>>      offset = offset_in_page(start_offset + start);
>>>
>>>

  reply	other threads:[~2019-07-26  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  5:27 [PATCH] btrfs: fix extent buffer read/write range checks Naohiro Aota
2019-07-26  5:38 ` Nikolay Borisov
2019-07-26  6:13   ` Naohiro Aota
2019-07-26  6:36     ` Qu Wenruo [this message]
2019-07-26  8:15       ` Naohiro Aota
2019-07-26  8:26         ` Qu Wenruo
2019-07-29  5:07         ` Qu Wenruo
2019-07-29  6:46           ` Nikolay Borisov
2019-07-29  6:54             ` Qu Wenruo

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=71f0399e-0719-ca8c-cb7b-aba5de5d0c5a@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=nborisov@suse.com \
    --cc=wqu@suse.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