Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 0/7] btrfs-progs: Fix wrong address accessing by subthread in btrfs-convert
Date: Mon, 27 Jul 2015 15:26:53 +0200	[thread overview]
Message-ID: <20150727132653.GC6306@twin.jikos.cz> (raw)
In-Reply-To: <cover.1437999624.git.zhaolei@cn.fujitsu.com>

On Mon, Jul 27, 2015 at 08:24:25PM +0800, Zhaolei wrote:
> From: Zhao Lei <zhaolei@cn.fujitsu.com>
> Zhao Lei (7):
>   btrfs-progs: Fix wrong address accessing by subthread in btrfs-convert
>   btrfs-progs: Move close timer handle code to line after sub process
>     exit
>   btrfs-progs: Remove cleanup-timer code for btrfs-convert
>   btrfs-progs: resst info->periodic.timer_fd's value after free
>   btrfs-progs: Set info->periodic.timer_fd to 0 in init-fail
>   btrfs-progs: Move code to create loop device to common
>   btrfs-progs: Introduce a misc test for thread conflict in
>     btrfs-convert

Replaced the existing and added the new ones, thanks!

      parent reply	other threads:[~2015-07-27 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 12:24 [PATCH v3 0/7] btrfs-progs: Fix wrong address accessing by subthread in btrfs-convert Zhaolei
2015-07-27 12:24 ` [PATCH v3 1/7] " Zhaolei
2015-07-27 12:24 ` [PATCH v3 2/7] btrfs-progs: Move close timer handle code to line after sub process exit Zhaolei
2015-07-27 12:24 ` [PATCH v3 3/7] btrfs-progs: Remove cleanup-timer code for btrfs-convert Zhaolei
2015-07-27 12:24 ` [PATCH v3 4/7] btrfs-progs: resst info->periodic.timer_fd's value after free Zhaolei
2015-07-27 12:24 ` [PATCH v3 5/7] btrfs-progs: Set info->periodic.timer_fd to 0 in init-fail Zhaolei
2015-07-27 12:24 ` [PATCH v3 6/7] btrfs-progs: Move code to create loop device to common Zhaolei
2015-07-27 12:24 ` [PATCH v3 7/7] btrfs-progs: Introduce a misc test for thread conflict in btrfs-convert Zhaolei
2015-07-27 13:26 ` David Sterba [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=20150727132653.GC6306@twin.jikos.cz \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zhaolei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox