On Thu, 13 Oct 2016 03:09:40 -0700 Li Qiang <liq...@gmail.com> wrote:
> From: Li Qiang <liqiang...@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.6...@mx.google.com> X-Google-Original-Message-ID: <1476353383-4679-1-git-send-email-Qiang(liqiang...@360.cn)> and patch 1/3 has that: In-Reply-To: <1476353383-4679-1-git-send-email-Qiang(liqiang...@360.cn)> References: <1476353383-4679-1-git-send-email-Qiang(liqiang...@360.cn)> Is it a "feature" of gmail to rewrite Message-ID headers ? Can it be turned off ? Cheers. -- Greg
