All of lore.kernel.org
 help / color / mirror / Atom feed
From: xfs@oss.sgi.com
To: xfs@oss.sgi.com
Subject: [XFS updates] XFS development tree branch, xfs-trans-recover-cleanup, created. v3.16-11801-gb818cca
Date: Sun, 28 Sep 2014 19:02:57 -0500 (CDT)	[thread overview]
Message-ID: <20140929000259.150717F84@oss.sgi.com> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "XFS development tree".

The branch, xfs-trans-recover-cleanup has been created
        at  b818cca1976d1a01754033ac08724e05d07cce8f (commit)

- Log -----------------------------------------------------------------
commit b818cca1976d1a01754033ac08724e05d07cce8f
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Sep 29 09:45:54 2014 +1000

    xfs: refactor recovery transaction start handling
    
    Rework the transaction lookup and allocation code in
    xlog_recovery_process_ophdr() to fold two related call-once
    helper functions into a single helper. Then fold in all the
    XLOG_START_TRANS logic to that helper to clean up the remaining
    logic in xlog_recovery_process_ophdr().
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

commit 76560669868d3b4d650d91d9bf467a8d81171766
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Sep 29 09:45:42 2014 +1000

    xfs: reorganise transaction recovery item code
    
    The code for managing transactions anf the items for recovery is
    spread across 3 different locations in the file. Move them all
    together so that it is easy to read the code without needing to jump
    long distances in the file.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

commit 88b863db97a18a04c90ebd57d84e1b7863114dcb
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Sep 29 09:45:32 2014 +1000

    xfs: fix double free in xlog_recover_commit_trans
    
    When an error occurs during buffer submission in
    xlog_recover_commit_trans(), we free the trans structure twice. Fix
    it by only freeing the structure in the caller regardless of the
    success or failure of the function.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

commit e9131e50f9d0a632e3011d73f283ba69be0cc682
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Sep 29 09:45:18 2014 +1000

    xfs: recovery of XLOG_UNMOUNT_TRANS leaks memory
    
    The XLOG_UNMOUNT_TRANS case skips the transaction, despite the fact
    an unmount record is always in a standalone transaction. Hence
    whenever we come across one of these we need to free the transaction
    structure associated with it as there is no commit record that
    follows it.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

commit eeb1168810d8a140f6834f8c4975f7bb3277d790
Author: Dave Chinner <dchinner@redhat.com>
Date:   Mon Sep 29 09:45:03 2014 +1000

    xfs: refactor xlog_recover_process_data()
    
    Clean up xlog_recover_process_data() structure in preparation for
    fixing the allocation and freeing context of the transaction being
    recovered.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Dave Chinner <david@fromorbit.com>

-----------------------------------------------------------------------


hooks/post-receive
-- 
XFS development tree

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2014-09-29  0:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140929000259.150717F84@oss.sgi.com \
    --to=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.