From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48542) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkYsK-0003z3-2i for qemu-devel@nongnu.org; Wed, 14 May 2014 09:05:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WkYsD-0000os-OJ for qemu-devel@nongnu.org; Wed, 14 May 2014 09:05:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39354) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkYsD-0000om-9w for qemu-devel@nongnu.org; Wed, 14 May 2014 09:05:29 -0400 Date: Wed, 14 May 2014 21:05:38 +0800 From: Fam Zheng Message-ID: <20140514130538.GA19672@T430.nay.redhat.com> References: <1399739757-3111-1-git-send-email-juli@redhat.com> <20140514124036.GD16683@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140514124036.GD16683@stefanha-thinkpad.redhat.com> Subject: Re: [Qemu-devel] [PATCH v3] snapshot: fixed bdrv_get_full_backing_filename can not get correct full_backing_filename List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: kwolf@redhat.com, junmuzi@gmail.com, Jun Li , qemu-devel@nongnu.org, stefanha@redhat.com On Wed, 05/14 14:40, Stefan Hajnoczi wrote: > On Sun, May 11, 2014 at 12:35:57AM +0800, Jun Li wrote: > > From: Jun Li > > > > This patch fixed the following bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=1084302 . > > > > path_combine can not calculate the correct full path name for backing_file. > > Such as: > > create a snapshot chain: > > sn2->sn1->$BASE_IMG > > backing file is : /home/wookpecker/img.qcow2 > > sn1 : /home/woodpecker/tmp/sn1 > > sn2 : /home/woodpecker/tmp/sn2 > > when create sn2, path_combine can not got a correct path for $BASE_IMG. > > > > In this patch, will check the backing_filename is a symlink or not firstly, > > then return the full(absolute) path via realpath. > > > > Signed-off-by: Jun Li > > --- > > block.c | 18 +++++++++++++++++- > > 1 file changed, 17 insertions(+), 1 deletion(-) > > Please fix your patch email submission process so it doesn't send the > same patch multiple times. > > You've done this several times in the past. It makes patch review more > difficult than it needs to be for reviewers. If I have to compare > several emails and figure out which patch is the right one before > reviewing I'm inclined not to review at all. > This is indeed very confusing. (I've showed Jun the configuration I have to send patches.) If you hit enter too quickly or forgot something, it's OK to try again, but using distinct subjects is important and makes it easier for us to know what's happening. If, by mistake the subjects you send are the same, please reply yourself to the list, saying "please ignore this one", so we know which to look at. Fam