Hello, On úterý 13. prosince 2016 16:59:26 CET Christoph Hellwig wrote: > --- > fs/xfs/libxfs/xfs_alloc.c | 78 ++++++++ +-------------------------------------- > fs/xfs/libxfs/xfs_alloc.h | 2 +- > 2 files changed, 16 insertions(+), 64 deletions(-) > > diff --git a/fs/xfs/libxfs/xfs_alloc.c b/fs/xfs/libxfs/xfs_alloc.c > index 91a6c17..87328a8 100644 > --- a/fs/xfs/libxfs/xfs_alloc.c > +++ b/fs/xfs/libxfs/xfs_alloc.c > @@ -1149,11 +1104,6 @@ xfs_alloc_ag_vextent_near( > XFS_WANT_CORRUPTED_GOTO(args->mp, i == 1, error0); > ASSERT(ltbno + ltlen <= be32_to_cpu(XFS_BUF_TO_AGF(args->agbp)- >agf_length)); > args->len = blen; > - if (!xfs_alloc_fix_minleft(args)) { > - xfs_btree_del_cursor(cnt_cur, XFS_BTREE_NOERROR); > - trace_xfs_alloc_near_nominleft(args); > - return 0; > - } > blen = args->len; > /* > * We are allocating starting at bnew for blen blocks. Doesn't this produce this code? args->len = blen; blen = args->len; Libor -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html