From: Carlos Maiolino <cmaiolino@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfsprogs libxfs-4.19-sync branch rebased
Date: Thu, 27 Sep 2018 12:13:01 +0200 [thread overview]
Message-ID: <20180927101301.we7iviepwxb6lqnq@odin.usersys.redhat.com> (raw)
In-Reply-To: <193ea177-7759-f501-2c24-d03be6904a8f@sandeen.net>
On Wed, Sep 26, 2018 at 02:12:46PM -0500, Eric Sandeen wrote:
> Hi all -
>
> I've rebased the libxfs-4.19-sync branch with some minor fixes (below).
>
> The head of the libxfs-4.19-sync branch is commit:
>
> a891cd6 xfs: fix a null pointer dereference in xfs_bmap_extents_to_btree
>
> This is still just a backport of the kernel libxfs. I'll get to Darrick's
> transaction cleanups on top of this soon, but I was trying to stick with
> the standard "update libxfs, then get to everything else" approach.
>
> I'll push this to for-next and tag it with an -rc0 in the next day or so,
> barring any disasters.
>
> Thanks,
> -Eric
>
\o/ better late than never
Whole series looks ok, you can add:
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> changes since the last push:
>
> diff -Nurp xfsprogs-maint-clean/libxfs/libxfs_priv.h xfsprogs-maint/libxfs/libxfs_priv.h
> --- xfsprogs-maint-clean/libxfs/libxfs_priv.h 2018-09-02 23:09:54.825409402 -0500
> +++ xfsprogs-maint/libxfs/libxfs_priv.h 2018-09-26 14:11:08.805788185 -0500
> @@ -563,7 +563,7 @@ int libxfs_zero_extent(struct xfs_inode
>
>
> bool xfs_log_check_lsn(struct xfs_mount *, xfs_lsn_t);
> -#define xfs_log_in_recovery(mp) false
> +#define xfs_log_in_recovery(mp) (false)
>
> /* xfs_icache.c */
> #define xfs_inode_set_cowblocks_tag(ip) do { } while (0)
> Binary files xfsprogs-maint-clean/libxfs/list_sort.o and xfsprogs-maint/libxfs/list_sort.o differ
> Binary files xfsprogs-maint-clean/libxfs/radix-tree.o and xfsprogs-maint/libxfs/radix-tree.o differ
> diff -Nurp xfsprogs-maint-clean/libxfs/trans.c xfsprogs-maint/libxfs/trans.c
> --- xfsprogs-maint-clean/libxfs/trans.c 2018-09-02 23:09:54.826409407 -0500
> +++ xfsprogs-maint/libxfs/trans.c 2018-09-26 14:10:37.664613207 -0500
> @@ -80,6 +80,8 @@ libxfs_trans_roll(
> struct xfs_trans *trans = *tpp;
> struct xfs_trans_res tres;
> unsigned int old_blk_res;
> + xfs_fsblock_t old_firstblock;
> + struct list_head old_dfops;
> int error;
>
> /*
> @@ -89,6 +91,9 @@ libxfs_trans_roll(
> tres.tr_logres = trans->t_log_res;
> tres.tr_logcount = trans->t_log_count;
> old_blk_res = trans->t_blk_res;
> + old_firstblock = trans->t_firstblock;
> + /* structure copy */
> + old_dfops = trans->t_dfops;
>
> /*
> * Commit the current transaction.
> @@ -113,6 +118,9 @@ libxfs_trans_roll(
> error = libxfs_trans_alloc(mp, &tres, 0, 0, 0, tpp);
> trans = *tpp;
> trans->t_blk_res = old_blk_res;
> + trans->t_firstblock = old_firstblock;
> + /* structure copy */
> + trans->t_dfops = old_dfops;
>
> return 0;
> }
> @@ -156,6 +164,8 @@ libxfs_trans_alloc(
> ptr->t_mountp = mp;
> ptr->t_blk_res = blocks;
> INIT_LIST_HEAD(&ptr->t_items);
> + INIT_LIST_HEAD(&ptr->t_dfops);
> + ptr->t_firstblock = NULLFSBLOCK;
> #ifdef XACT_DEBUG
> fprintf(stderr, "allocated new transaction %p\n", ptr);
> #endif
>
--
Carlos
prev parent reply other threads:[~2018-09-27 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 19:12 [ANNOUNCE] xfsprogs libxfs-4.19-sync branch rebased Eric Sandeen
2018-09-27 10:13 ` Carlos Maiolino [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180927101301.we7iviepwxb6lqnq@odin.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).