From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2] jbd2: fix r_count overflows leading to buffer overflow in journal recovery
Date: Thu, 14 May 2015 19:12:42 -0400 [thread overview]
Message-ID: <20150514231242.GD3901@thunk.org> (raw)
In-Reply-To: <20150514204826.GA17985@quack.suse.cz>
On Thu, May 14, 2015 at 10:48:26PM +0200, Jan Kara wrote:
> On Thu 14-05-15 12:34:24, Darrick J. Wong wrote:
> > The journal revoke block recovery code does not check r_count for
> > sanity, which means that an evil value of r_count could result in
> > the kernel reading off the end of the revoke table and into whatever
> > garbage lies beyond. This could crash the kernel, so fix that.
> >
> > However, in testing this fix, I discovered that the code to write
> > out the revoke tables also was not correctly checking to see if the
> > block was full -- the current offset check is fine so long as the
> > revoke table space size is a multiple of the record size, but this
> > is not true when either journal_csum_v[23] are set.
> >
> > v2: The comparison on the revoke block writer code should allow the
> > revoke block to become totally full.
> >
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> Looks good. You can add:
> Reviewed-by: Jan Kara <jack@suse.cz>
Thanks, applied.
- Ted
prev parent reply other threads:[~2015-05-14 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:34 [PATCH v2] jbd2: fix r_count overflows leading to buffer overflow in journal recovery Darrick J. Wong
2015-05-14 20:48 ` Jan Kara
2015-05-14 23:12 ` 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=20150514231242.GD3901@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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.