linux-ext4 - Re: [PATCH v2 0/5] ext4: try to fix up es regressions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130311062306.GA3948@gmail.com>
Date:	Mon, 11 Mar 2013 14:23:06 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	Theodore Ts'o <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org, Zheng Liu <wenqing.lz@...bao.com>,
	Dmitry Monakhov <dmonakhov@...nvz.org>
Subject: Re: [PATCH v2 0/5] ext4: try to fix up es regressions

On Sun, Mar 10, 2013 at 10:11:08PM -0400, Theodore Ts'o wrote:
> I've placed these patches (with a few minor fixups) on the dev branch,
> and will start running a test/verification run on them).  Thanks for
> working on these patches!

Thanks.

As Dmitry's comment, I have updated my patches.

In patch 2 (ext4: add self-testing infrastructure to do a sanity check)
Dmitry suggests that we'd better replace 'retval != map->m_len' condition
with a BUG_ON().  But now I don't think we need to touch it because we
are still discussing this assumption.

In patch 4 (ext4: update extent status tree after an extent is zeroed
out) I have moved ext4_es_zeroout() into extents.c file and remove some
local variables that are only used once.  Do I need to send it out?  I
know the test has started.  Maybe I should wait a moment, and let the
tree stable before -rc2.

Regards,
                                                - Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html