From: Juan Quintela <quintela@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Ryan Harper <ryanh@us.ibm.com>,
Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 3/3] raw-posix: Re-open host CD-ROM after media change
Date: Thu, 24 Mar 2011 22:23:51 +0100 [thread overview]
Message-ID: <m3bp10gql4.fsf@neno.mitica> (raw)
In-Reply-To: <AANLkTiky3OmOzQ87QANjv0gohbt-8jyaK0UfuQZqQ_6G@mail.gmail.com> (Stefan Hajnoczi's message of "Thu, 24 Mar 2011 19:00:21 +0000")
Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Thu, Mar 24, 2011 at 12:42 PM, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 23.03.2011 21:50, schrieb Stefan Hajnoczi:
>>> On Wed, Mar 23, 2011 at 8:27 PM, Juan Quintela <quintela@redhat.com> wrote:
>>>> Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> wrote:
>>>>> +
>>>>> + if (s->fd == -1) {
>>>>> + s->fd = qemu_open(bs->filename, s->open_flags, 0644);
>>>>
>>>> Everything else on that file uses plain "open" not "qemu_open".
>>>> diference is basically that qemu_open() adds flag O_CLOEXEC.
>>>>
>>>> I don't know if this one should be vanilla open or the other ones
>>>> qemu_open().
>>>>
>>>> What do you think?
>>>
>>> raw_open_common() uses qemu_open(). That's why I used it.
>>
>> And I think it's correct. There's no reason not to set O_CLOEXEC here.
>> Maybe some of the open() users need to be fixed.
I didn't doubt that. What I tried to point is that there are three
opens for cdrom/floppy on that file. It makes sense that all are the
same. I guessed that proper fix was to change all others to
qemu_open(), but just wanted to point that it was inconsistent, and
should be done one or other way.
>>>>> + if (s->fd < 0) {
>>>>> + return 0;
>>>>> + }
>>>>> + }
>>>>> +
>>>>> + ret = (ioctl(s->fd, CDROM_DRIVE_STATUS, CDSL_CURRENT) == CDS_DISC_OK);
>>>>
>>>> parens are not needed around ==.
>>>
>>> Yes, if you want I'll remove them. I just did it for readability.
>>
>> I like them.
>
> I will have to #ifdef QUINTELA and #ifdef KWOLF :). Seriously, I'll
> leave the braces unless anyone feels really strongly either way. This
> passes checkpatch.pl BTW.
In
x = (a == b);
braces are useless. But my preference is not 'strong' enough to try to
force it on other people.
It appears that other people feel strong about it, so let it be.
Later, Juan.
prev parent reply other threads:[~2011-03-24 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 17:40 [Qemu-devel] [PATCH 0/3] block: Correct size across CD-ROM media change Stefan Hajnoczi
2011-03-23 17:40 ` [Qemu-devel] [PATCH 1/3] trace: Trace bdrv_set_locked() Stefan Hajnoczi
2011-03-23 17:40 ` [Qemu-devel] [PATCH 2/3] block: Do not cache device size for removable media Stefan Hajnoczi
2011-03-23 20:18 ` [Qemu-devel] " Juan Quintela
2011-03-23 20:46 ` Stefan Hajnoczi
2011-03-23 17:40 ` [Qemu-devel] [PATCH 3/3] raw-posix: Re-open host CD-ROM after media change Stefan Hajnoczi
2011-03-23 20:27 ` [Qemu-devel] " Juan Quintela
2011-03-23 20:50 ` Stefan Hajnoczi
2011-03-24 12:42 ` Kevin Wolf
2011-03-24 19:00 ` Stefan Hajnoczi
2011-03-24 21:23 ` Juan Quintela [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=m3bp10gql4.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).