From: Jan Kara <jack@suse.cz>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu, jack@suse.cz,
adilger@dilger.ca
Subject: Re: [PATCH] ext4: ext4_mb_seq_groups_show: Fix stack memory corruption
Date: Tue, 8 Nov 2016 10:21:15 +0100 [thread overview]
Message-ID: <20161108092115.GG32353@quack2.suse.cz> (raw)
In-Reply-To: <1478501141-15651-1-git-send-email-chandan@linux.vnet.ibm.com>
On Mon 07-11-16 12:15:41, Chandan Rajendra wrote:
> The number of 'counters' elements needed in 'struct sg' is
> super_block->s_blocksize_bits + 2. Presently we have 16 'counters'
> elements in the array. This is insufficient for block sizes >= 32k. In
> such cases the memcpy operation performed in ext4_mb_seq_groups_show()
> would cause stack memory corruption.
>
> Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
> ---
> fs/ext4/mballoc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index a937ac7..67e6fcb 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2287,7 +2287,7 @@ static int ext4_mb_seq_groups_show(struct seq_file *seq, void *v)
> struct ext4_group_info *grinfo;
> struct sg {
> struct ext4_group_info info;
> - ext4_grpblk_t counters[16];
> + ext4_grpblk_t counters[16 + 2];
How about using EXT4_MAX_BLOCK_LOG_SIZE + 2? It would be somewhat clearer
what that means... Having a function returning number of buddy counters in
a group info would be even better (and a constant for maximum number of
counters) but that's an independent cleanup...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-11-08 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 6:45 [PATCH] ext4: ext4_mb_seq_groups_show: Fix stack memory corruption Chandan Rajendra
2016-11-08 9:21 ` Jan Kara [this message]
2016-11-10 5:44 ` Chandan Rajendra
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=20161108092115.GG32353@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger@dilger.ca \
--cc=chandan@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).