[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mwuqmzoe.fsf@openvz.org>
Date: Wed, 27 Feb 2013 03:18:57 +0400
From: Dmitry Monakhov <dmonakhov@...nvz.org>
To: Theodore Ts'o <tytso@....edu>
Cc: linux-ext4@...r.kernel.org, Zheng Liu <gnehzuil.liu@...il.com>
Subject: [PATCH] jbd2: Fix ERR_PTR dereference in jbd2__journal_start
On Fri, 22 Feb 2013 13:03:25 -0500, "Theodore Ts'o" <tytso@....edu> wrote:
> On Fri, Feb 22, 2013 at 09:17:57PM +0400, Dmitry Monakhov wrote:
> >
> > 301'th xfstests are failed due to :
> > commit d100eef2440fea13e4f09e88b1c8bcbca64beb9f
> > Author: Zheng Liu <wenqing.lz@...bao.com>
> > Date: Mon Feb 18 00:29:59 2013 -0500
> >
> > ext4: lookup block mapping in extent status tree
> >
> > TESTCASE: https://github.com/dmonakhov/xfstests/commit/7b7efeee30a41109201e2040034e71db9b66ddc0
>
> Thanks for the heads up. I haven't updatied the xfstests I've been
> using yet, since I want to make sure I'm comparing apples and oranges
> during the merge window when I'm checking for regressions; I'll update
> my xfstests in a week or two after the merge window settles down, and
> then I'll rerun my baseline tests using the updated xfstests against
> 3.8.0 and 3.9-rc2 or 3.9-rc3.
Ohh. I've found that 303'th test failed for 304e220f0(ext4_for_linus)
EIO result in OOPS due to ERR_PTR dereference see patch attached
It is bad luck that it was not triggered before, but it is always hard
to have good coverage for such dark corners. Obviously this type of
mistypes should be spotted by one of Julia Lawall's magic scripts
I'll check that and try to write new one if it not exist yet.
View attachment "0001-jbd2-Fix-ERR_PTR-dereference-in-jbd2__journal_start.patch" of type "text/x-patch" (1790 bytes)
>
> (And furthermore, these new xfstests aren't yet in xfstests upstream
> yet, right? Any comments from the xfstests maintainer about whether
> they are going to be willing to take your proposed new test cases?)
>
> So when you say this is a regression, I take it that this test #301
> doesn't fail on commit d100eef2440f^, but it does fail on d100eef2440f,
> correct?
>
> - Ted
Powered by blists - more mailing lists