From: Anand Jain <anand.jain@oracle.com>
To: miaox@cn.fujitsu.com
Cc: Chris Mason <clm@fb.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: fix null pointer dereference in clone_fs_devices when name is null
Date: Mon, 07 Jul 2014 17:20:57 +0800 [thread overview]
Message-ID: <53BA6679.7040906@oracle.com> (raw)
In-Reply-To: <53BA0E77.6040804@cn.fujitsu.com>
> It's a pity that the patch has been merged into the upstream kernel.
> Let's correct our miss before the next merge.
What I found were new-bugs, those are not related to this patch.
> BTW, I sent some patches to fix the problems about seed device(including
> the updated patch of this one), could you try them and confirm that they
> can fix the problems you said above or not?
>
> [PATCH V2 7/9] btrfs: fix null pointer dereference in clone_fs_devices when name is null
> [PATCH 8/9] Btrfs: fix unzeroed members in fs_devices when creating a fs from seed fs
> [PATCH 9/9] Btrfs: fix writing data into the seed filesystem
>
> This first one is the updated patch of this one.
With 8,9/9 it fixes the new-bugs as well. Thanks.
Anand
next prev parent reply other threads:[~2014-07-07 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 9:12 [PATCH 1/2] btrfs: fix null pointer dereference in clone_fs_devices when name is null Anand Jain
2014-06-30 9:12 ` [PATCH 2/2] btrfs: fix null pointer dereference in btrfs_show_devname " Anand Jain
2014-06-30 10:02 ` [PATCH 1/2] btrfs: fix null pointer dereference in clone_fs_devices " Miao Xie
2014-06-30 15:06 ` Anand Jain
2014-07-02 2:38 ` Miao Xie
2014-07-04 11:21 ` Anand Jain
2014-07-04 11:24 ` Anand Jain
2014-07-07 3:05 ` Miao Xie
2014-07-07 9:20 ` Anand Jain [this message]
2014-07-07 9:21 ` Anand Jain
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=53BA6679.7040906@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@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;
as well as URLs for NNTP newsgroup(s).