From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49531)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <groug@kaod.org>) id 1buef8-0006Ms-Sm
	for qemu-devel@nongnu.org; Thu, 13 Oct 2016 07:59:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <groug@kaod.org>) id 1buef4-0003ok-Uv
	for qemu-devel@nongnu.org; Thu, 13 Oct 2016 07:59:02 -0400
Received: from 10.mo179.mail-out.ovh.net ([46.105.79.46]:60597)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <groug@kaod.org>) id 1buef4-0003o7-PI
	for qemu-devel@nongnu.org; Thu, 13 Oct 2016 07:58:58 -0400
Received: from player792.ha.ovh.net (b7.ovh.net [213.186.33.57])
	by mo179.mail-out.ovh.net (Postfix) with ESMTP id CD9EAFFBCEB
	for <qemu-devel@nongnu.org>; Thu, 13 Oct 2016 13:58:57 +0200 (CEST)
Date: Thu, 13 Oct 2016 13:58:54 +0200
From: Greg Kurz <groug@kaod.org>
Message-ID: <20161013135854.2cf48a4d@bahia>
In-Reply-To: <57ff5d71.4a3c9d0a.90936.6097@mx.google.com>
References: <57ff5d71.4a3c9d0a.90936.6097@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v3 0/3] 9pfs: fix xattr related issues
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Li Qiang <liq3ea@gmail.com>
Cc: qemu-devel@nongnu.org, Li Qiang <liqiang6-s@360.cn>

On Thu, 13 Oct 2016 03:09:40 -0700
Li Qiang <liq3ea@gmail.com> wrote:

> From: Li Qiang <liqiang6-s@360.cn>
> 
> The current xattr implementation in 9pfs has several issues.
> 
> -The 'copied_len' in V9fsXattr is used both for accounting bytes and to tag the xattr fid.
> -The 'len/copied_len' field in V9fsXattr has a wrong type.
> -The read/write dispatch function of xattr uses unsafe computations.
> 
> This patchset solves these issues.
> 
> Li Qiang (3):
>   9pfs: add xattrwalk_fid field in V9fsXattr struct
>   9pfs: convert 'len/copied_len' field in V9fsXattr to the type of
>     uint64_t
>   9pfs: fix integer overflow issue in xattr read/write
> 
>  hw/9pfs/9p.c | 39 ++++++++++++++++-----------------------
>  hw/9pfs/9p.h |  5 +++--
>  2 files changed, 19 insertions(+), 25 deletions(-)
> 

Weird... the patches appear in separate threads, which is perturbing.

The cover letter has this:

Message-ID: <57ff5d71.4a3c9d0a.90936.6097@mx.google.com>
X-Google-Original-Message-ID: <1476353383-4679-1-git-send-email-Qiang(liqiang6-s@360.cn)>

and patch 1/3 has that:

In-Reply-To: <1476353383-4679-1-git-send-email-Qiang(liqiang6-s@360.cn)>
References: <1476353383-4679-1-git-send-email-Qiang(liqiang6-s@360.cn)>

Is it a "feature" of gmail to rewrite Message-ID headers ? Can it be turned off ?

Cheers.

--
Greg