From: liuxue <liuxueliu.liu@huawei.com>
To: Chao Yu <chao2.yu@samsung.com>, 'Yunlei He' <heyunlei@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org
Subject: Re: [PATCH] f2fs: add a max block count for f2fs_map_blocks
Date: Fri, 25 Dec 2015 18:17:27 +0800 [thread overview]
Message-ID: <567D17B7.7060308@huawei.com> (raw)
In-Reply-To: <018a01d13ef6$63c58120$2b508360$@samsung.com>
On 2015/12/25 17:25, Chao Yu wrote:
> Hi,
>
>> -----Original Message-----
>> From: Yunlei He [mailto:heyunlei@huawei.com]
>> Sent: Friday, December 25, 2015 4:48 PM
>> To: linux-f2fs-devel@lists.sourceforge.net; jaegeuk@kernel.org; chao2.yu@samsung.com
>> Cc: bintian.wang@huawei.com; Yunlei He; Xue Liu
>> Subject: [PATCH] f2fs: add a max block count for f2fs_map_blocks
>>
>> This patch adds a max block count for f2fs_map_blocks
>
> Maximum file size should be limited by sb->s_maxbytes which was inited
> in max_file_size(), so logical block index should not exceed the value
> calculated with maxbytes, why would we limit logical block index with
> another value?
>
> Thanks,
>
Hi,
Trinity test program will send a block number as parameter into ioctl_fibmap, which will be used in
get_node_path(), when the block number large than f2fs max blocks, it will trigger kernel bug.
So we judge the block number in f2fs_map_blocks(), which reference ext4:
file: fs/ext4/inode.c
function: ext4_map_blocks()
/* We can handle the block number less than EXT_MAX_BLOCKS */
if (unlikely(map->m_lblk >= EXT_MAX_BLOCKS))
return -EFSCORRUPTED;
>>
>> Signed-off-by: Yunlei He <heyunlei@huawei.com>
>> Signed-off-by: Xue Liu <liuxueliu.liu@huawei.com>
>> ---
>> fs/f2fs/data.c | 4 ++++
>> fs/f2fs/f2fs.h | 3 +++
>> 2 files changed, 7 insertions(+)
>>
>> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
>> index e34b1bd..2a16c867 100644
>> --- a/fs/f2fs/data.c
>> +++ b/fs/f2fs/data.c
>> @@ -578,6 +578,10 @@ int f2fs_map_blocks(struct inode *inode, struct f2fs_map_blocks *map,
>> map->m_len = 0;
>> map->m_flags = 0;
>>
>> + /* We can handle the block number less than F2FS_MAX_BLOCKS */
>> + if (unlikely(map->m_lblk >= F2FS_MAX_BLOCKS))
>> + return -EUCLEAN;
>> +
>> /* it only supports block size == page size */
>> pgofs = (pgoff_t)map->m_lblk;
>>
>> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
>> index 19beabe..911c99b 100644
>> --- a/fs/f2fs/f2fs.h
>> +++ b/fs/f2fs/f2fs.h
>> @@ -331,6 +331,9 @@ enum {
>>
>> #define F2FS_LINK_MAX 0xffffffff /* maximum link count per file */
>>
>> +
>> +#define F2FS_MAX_BLOCKS 0x3F015AFF /* maximum block count per file */
>> +
>> #define MAX_DIR_RA_PAGES 4 /* maximum ra pages of dir */
>>
>> /* vector size for gang look-up from extent cache that consists of radix tree */
>> --
>> 1.9.1
>
>
>
> .
>
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-12-25 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 8:47 [PATCH] f2fs: add a max block count for f2fs_map_blocks Yunlei He
2015-12-25 9:25 ` Chao Yu
2015-12-25 10:17 ` liuxue [this message]
2015-12-26 13:21 ` Chao Yu
2015-12-28 13:03 ` He YunLei
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=567D17B7.7060308@huawei.com \
--to=liuxueliu.liu@huawei.com \
--cc=chao2.yu@samsung.com \
--cc=heyunlei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.