On Fri, Mar 28, 2014 at 12:33:34PM -0500, Mark Tinguely wrote:
> Fix the fix directory "bad hash ordering" bug introduced in
> commit f5ea1100.
The patch looks like it fixes a hashing issue, but I really can't
tell what hashing issue it fixes from the commit message.
I don't know if you've identified the right commit just by looking
at it - to confirm you've quoted the correct hash I have to find it,
parse it, read the diff and try and work out whether it could have
introduced some bug that you haven't described....
.... introduced in commit f5ea110 ("xfs: add CRCs to dir2/da node
blocks") ....
is far more informative, even for the causal reader....
Secondly, reading that commit subject and message in isolation,
it didn't even occur to me that this is a fix for a filesystem
corruption bug. Any distro maintainer reading the commit logs won't
have any idea that they need to pick this up, either.
IOWs, it is extremely important that the commit message for a
filesystem corruption bug fix to be clearly marked as fixing a
corruption bug, explain what the bug is, what they user visible
symptoms are, what the impact of the corruption is, how likely users
are going to be impacted by it, whether is causes permanent loss
of data or not, etc. This doesn't belong in a throw-away comment to
your fix...
> ---
> A C program that generates this problem can be found at:
> http://oss.sgi.com/archives/xfs/2014-03/msg00373.html
>
> A xfstest for this bug is coming from Hannes Frederic Sowa.
Can you convert this program to an xfstest yourself so that I can
commit the regression test at the same time I commit an updated
fix?
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html