From: Theodore Ts'o <tytso@mit.edu>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-ext4@vger.kernel.org, "Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH] ext4: verify extent header depth
Date: Fri, 15 Jul 2016 00:22:48 -0400 [thread overview]
Message-ID: <20160715042248.GD26465@thunk.org> (raw)
In-Reply-To: <20160707005447.GA19871@thunk.org>
On Wed, Jul 06, 2016 at 08:54:47PM -0400, Theodore Ts'o wrote:
> So we could arbitrarily limit eh_depth to say, 32 levels, or some
> such. That will prevent the malicious corruption, while also making
> it very difficult for the malicious fallocate/punch hole workload
> scenario to be triggered.
I've decided to apply your patch with the limit raised to 32. That
should be enough to prevent the malicious corruption cases.
- Ted
prev parent reply other threads:[~2016-07-15 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 21:27 [PATCH] ext4: verify extent header depth Vegard Nossum
2016-07-06 22:23 ` Vegard Nossum
2016-07-06 22:28 ` Darrick J. Wong
2016-07-07 0:54 ` Theodore Ts'o
2016-07-15 4:22 ` Theodore 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=20160715042248.GD26465@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).