All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Use of PATH_MAX
Date: Fri, 16 May 2008 09:32:53 -0500	[thread overview]
Message-ID: <482D9B15.7050209@codemonkey.ws> (raw)
In-Reply-To: <18477.39195.224231.369929@mariner.uk.xensource.com>

Ian Jackson wrote:
> iwj writes ("Re: [Qemu-devel] Use of PATH_MAX"):
>   
>> I agree that it would be better to get rid of the static buffers.  But
>> at the moment I'm just trying to stop a tide of PATH_MAX nonsense
>> enveloping the Xen semi-fork.  [...]
>>     
>
> Sorry, let me be clearer: in the Xen version of qemu, which I'm trying
> to bring more into line with upstream, people are seeing PATH_MAX in
> some places and changing fixed constants 1024 to PATH_MAX because they
> think that PATH_MAX is the right thing to do.
>
> If I can get agreement on a new name to use in qemu proper then it
> will be easy to change to use that everywhere.
>
> Of course if someone wants to do the work to make the buffers dynamic
> then that is good but that's quite a bit of work and is likely to
> introduce the occasional memory management bug, so I don't think that
> changing 1024 and PATH_MAX to QEMU_PATH_MAX should wait for it.
>   

I don't see any value in converting PATH_MAX to QEMU_PATH_MAX.

Both are equally wrong.

Regards,

Anthony Liguori

> Ian.
>
>
>   

  reply	other threads:[~2008-05-16 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 13:35 [Qemu-devel] Use of PATH_MAX Ian Jackson
2008-05-16 14:00 ` Anthony Liguori
2008-05-16 14:09   ` Warner Losh
2008-05-16 14:35     ` Anthony Liguori
2008-05-16 14:52       ` Ian Jackson
2008-05-16 14:02 ` Paul Brook
2008-05-16 14:21   ` Ian Jackson
2008-05-16 14:24     ` Ian Jackson
2008-05-16 14:32       ` Anthony Liguori [this message]
2008-05-16 14:46         ` Ian Jackson

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=482D9B15.7050209@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=paul@codesourcery.com \
    --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.