From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
Cc: alsa-devel@alsa-project.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
kernel-janitors@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
sound-open-firmware@alsa-project.org
Subject: Re: [PATCH 2/2] ASoC: SOF: sof-client-probes: cleanup tokenize_input()
Date: Wed, 6 Jul 2022 13:44:43 +0300 [thread overview]
Message-ID: <20220706104443.GE2338@kadam> (raw)
In-Reply-To: <2d7bb9f7-a316-16d8-b290-e0cae9b28127@linux.intel.com>
On Wed, Jul 06, 2022 at 12:27:49PM +0300, Péter Ujfalusi wrote:
>
>
> On 06/07/2022 10:25, Dan Carpenter wrote:
> > The tokenize_input() function is cleaner if it uses strndup_user()
> > instead of simple_write_to_buffer(). The way it's written now, if
> > *ppos is non-zero then it returns -EIO but normally we would return
> > 0 in that case. It's easier to handle that in the callers.
>
> This patch breaks the probe point settings:
>
> # echo 52,1,0 > /sys/kernel/debug/sof/probe_points
> -bash: echo: write error: Invalid argument
>
> I did not looked for the exact reason, but something is not correct.
>
Crud...
Thanks for testing.
I used strndup_user() in a couple other patches today and I didn't
realize how strict it was. I've NAKed my patches which used
strndup_user(). One of the patches was an infoleak patch so I'm going
to resend that using memdup_user() instead but let's just drop this one.
I guess another safer option would be to just always zero the buffers
going into simple_write_to_buffer()...
regards,
dan carpenter
next prev parent reply other threads:[~2022-07-06 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 7:23 [PATCH 1/2] ASoC: SOF: sof-client-probes: fix error codes in sof_probes_compr_copy() Dan Carpenter
2022-07-06 7:25 ` [PATCH 2/2] ASoC: SOF: sof-client-probes: cleanup tokenize_input() Dan Carpenter
2022-07-06 9:27 ` Péter Ujfalusi
2022-07-06 10:44 ` Dan Carpenter [this message]
2022-07-06 10:56 ` Cezary Rojewski
2022-07-06 9:05 ` [PATCH 1/2] ASoC: SOF: sof-client-probes: fix error codes in sof_probes_compr_copy() Péter Ujfalusi
2022-07-06 10:00 ` Péter Ujfalusi
2022-07-06 10:21 ` Dan Carpenter
2022-07-06 10:31 ` Dan Carpenter
2022-07-06 10:36 ` Dan Carpenter
2022-07-06 10:41 ` Péter Ujfalusi
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=20220706104443.GE2338@kadam \
--to=dan.carpenter@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.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