All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Qiang <liq3ea@gmail.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, Li Qiang <liqiang6-s@360.cn>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] 9pfs: fix xattr related issues
Date: Thu, 13 Oct 2016 20:10:17 +0800	[thread overview]
Message-ID: <CAKXe6S+VviUvJobMm7FmvWiUAEjEOPoaWfMjOjk6hAdrFV+00g@mail.gmail.com> (raw)
In-Reply-To: <20161013135854.2cf48a4d@bahia>

I'm not sure of this, I use

git format-patch -3 -s --subject-prefix="PATCH v3" --cover-letter

to generate this patchset first and then modify some text. Then

git send-email *.patch --to xx --to

Is there anything wrong?

On 2016-10-13 19:58 GMT+08:00 Greg Kurz <groug@kaod.org> wrote:

> 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
>

  reply	other threads:[~2016-10-13 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 10:09 [Qemu-devel] [PATCH v3 0/3] 9pfs: fix xattr related issues Li Qiang
2016-10-13 11:58 ` Greg Kurz
2016-10-13 12:10   ` Li Qiang [this message]
2016-10-13 12:19     ` Greg Kurz
2016-10-13 12:33       ` Li Qiang

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=CAKXe6S+VviUvJobMm7FmvWiUAEjEOPoaWfMjOjk6hAdrFV+00g@mail.gmail.com \
    --to=liq3ea@gmail.com \
    --cc=groug@kaod.org \
    --cc=liqiang6-s@360.cn \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.