From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dan Carpenter <error27@gmail.com>
Cc: alsa-devel@alsa-project.org, Jassi Brar <jassi.brar@samsung.com>,
Takashi Iwai <tiwai@suse.de>,
kernel-janitors@vger.kernel.org,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [patch] ASoC: soc: snprintf() doesn't return negative
Date: Mon, 11 Oct 2010 10:40:09 +0000 [thread overview]
Message-ID: <20101011104009.GB9231@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101011035416.GD5851@bicker>
On Mon, Oct 11, 2010 at 05:54:17AM +0200, Dan Carpenter wrote:
> In user space snprintf() returns negative on errors but the kernel
> version only returns positives. It could potentially return sizes
I'm not going to apply this. snprintf() returns a signed type, checking
that the return value is a reasonable thing to do here - at worst we're
wasting a few cycles in code that's nowhere near a hot path, at best
we're robust in the face of a decision to add error reporting to
snprintf() so it's hard to see this change as an improvement.
> larger than the size of the buffer so we should check for that.
> - if (ret >= 0)
> - ret = simple_read_from_buffer(user_buf, count, ppos, buf, ret);
> + if (ret > PAGE_SIZE)
> + ret = PAGE_SIZE;
> +
> + ret = simple_read_from_buffer(user_buf, count, ppos, buf, ret);
The PAGE_SIZE part of the change has an issue too, the code immediately
preceeding this is:
list_for_each_entry(codec, &codec_list, list)
ret += snprintf(buf + ret, PAGE_SIZE - ret, "%s\n",
codec->name);
so it's rather late to be worrying about PAGE_SIZE after the loop.
Please also try to be a bit more thoughtful in your use of
get_maintainers; try to have a look at why people have come up and
consider if it's really sensible to include them.
next prev parent reply other threads:[~2010-10-11 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 3:54 [patch] ASoC: soc: snprintf() doesn't return negative Dan Carpenter
2010-10-11 10:07 ` Liam Girdwood
2010-10-11 10:40 ` Mark Brown [this message]
2010-10-11 16:40 ` Dan Carpenter
2010-10-11 18:51 ` Mark Brown
2010-10-11 19:45 ` Dan Carpenter
2010-10-11 20:57 ` Takashi Iwai
2010-10-12 9:35 ` Mark Brown
2010-10-12 9:49 ` Takashi Iwai
2010-10-12 9:56 ` Mark Brown
2010-10-12 10:40 ` Dan Carpenter
2010-10-11 21:11 ` Dan Carpenter
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=20101011104009.GB9231@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=error27@gmail.com \
--cc=jassi.brar@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.com \
--cc=tiwai@suse.de \
/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