From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, Jaco Kroon <jaco@uls.co.za>,
stable@vger.kernel.org
Subject: Re: [PATCH] ext4: Forbid overflowing inode count when resizing
Date: Fri, 25 May 2018 12:50:57 -0400 [thread overview]
Message-ID: <20180525165057.GC8197@thunk.org> (raw)
In-Reply-To: <20180524113646.3859-1-jack@suse.cz>
On Thu, May 24, 2018 at 01:36:46PM +0200, Jan Kara wrote:
> ext4_resize_fs() has an off-by-one bug when checking whether growing of
> a filesystem will not overflow inode count. As a result it allows a
> filesystem with 8192 inodes per group to grow to 64TB which overflows
> inode count to 0 and makes filesystem unusable. Fix it.
>
> CC: stable@vger.kernel.org
> Fixes: 3f8a6411fbada1fa482276591e037f3b1adcf55b
> Reported-by: Jaco Kroon <jaco@uls.co.za>
> Signed-off-by: Jan Kara <jack@suse.cz>
Applied, thanks.
- Ted
prev parent reply other threads:[~2018-05-25 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 11:36 [PATCH] ext4: Forbid overflowing inode count when resizing Jan Kara
2018-05-24 13:52 ` Jaco Kroon
2018-05-24 14:09 ` Jan Kara
2018-05-24 14:09 ` Jan Kara
2018-05-24 16:44 ` Andreas Dilger
2018-05-25 16:50 ` Theodore Y. Ts'o [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=20180525165057.GC8197@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=jaco@uls.co.za \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@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 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.