From: Paolo Bonzini <pbonzini@redhat.com>
To: xen-devel@lists.xensource.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: xenfs: implement O_NONBLOCK for /proc/xen/xenbus
Date: Mon, 26 Jul 2010 11:33:10 +0200 [thread overview]
Message-ID: <4C4D5656.7050100@redhat.com> (raw)
In-Reply-To: <4C2DCD76.8070101@redhat.com>
On 07/02/2010 01:28 PM, Paolo Bonzini wrote:
> On 06/28/2010 09:53 AM, Paolo Bonzini wrote:
>> On 06/26/2010 06:10 PM, Jeremy Fitzhardinge wrote:
>>> On 06/24/2010 05:32 PM, Paolo Bonzini wrote:
>>>> Trivial patch. Tested only in the pvops version.
>>>
>>> What user do you have for this?
>>
>> It was reported by internal QE without many details, likely it was found
>> by code inspection or some automated tool. I didn't ask because the
>> patch was easy enough, but I can get more information if you care.
>
> It was found by a test (proc01) in LTP to read every entry of the procfs.
ping? It's not in linux-2.6.18.hg either.
Paolo
prev parent reply other threads:[~2010-07-26 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 16:32 xenfs: implement O_NONBLOCK for /proc/xen/xenbus Paolo Bonzini
2010-06-26 16:10 ` Jeremy Fitzhardinge
2010-06-28 7:53 ` Paolo Bonzini
2010-07-02 11:28 ` Paolo Bonzini
2010-07-26 9:33 ` Paolo Bonzini [this message]
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=4C4D5656.7050100@redhat.com \
--to=pbonzini@redhat.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.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 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.