[PATCH 2/9] xfs: fix incorrect remote symlink block count
Ben Myers
bpm at sgi.com
Thu May 30 12:49:32 CDT 2013
On Wed, May 29, 2013 at 12:39:33PM -0400, Brian Foster wrote:
> On 05/27/2013 02:38 AM, Dave Chinner wrote:
> > From: Dave Chinner <dchinner at redhat.com>
> >
> > When CRCs are enabled, the number of blocks needed to hold a remote
> > symlink on a 1k block size filesystem may be 2 instead of 1. The
> > transaction reservation for the allocated bloks was not taking this
> > into account and only allocating one block. hence when trying to
> > read or invalidate such symlinks, we are mapping a hole where there
> > should be a block and things go bad at that point.
> >
> > Fix the reservation to use the correct block count, clean up the
> > block count calculation similar to the remote attribute calculation,
> > and add a debug guard to detect when we don't write the entire
> > symlink to disk.
> >
> > Signed-off-by: Dave Chinner <dchinner at redhat.com>
> > ---
>
> Reviewed-by: Brian Foster <bfoster at redhat.com>
Applied.
More information about the xfs
mailing list