From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: Eliad Peller <eliad@wizery.com>
Subject: Re: [PATCH 1/3] mac80211: fix some snprintf misuses
Date: Tue, 01 Oct 2013 12:16:43 +0200 [thread overview]
Message-ID: <1380622603.14430.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1377852561-16754-1-git-send-email-johannes@sipsolutions.net> (sfid-20130830_104931_636456_970396D8)
On Fri, 2013-08-30 at 10:49 +0200, Johannes Berg wrote:
> From: Eliad Peller <eliad@wizery.com>
>
> In some debugfs related functions snprintf was used
> while scnprintf should have been used instead.
>
> (blindly adding the return value of snprintf and supplying
> it to the next snprintf might result in buffer overflow when
> the input is too big)
Applied.
johannes
prev parent reply other threads:[~2013-10-01 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 8:49 [PATCH 1/3] mac80211: fix some snprintf misuses Johannes Berg
2013-08-30 8:49 ` [PATCH 2/3] ieee80211: fix vht cap definitions Johannes Berg
2013-10-01 10:17 ` Johannes Berg
2013-08-30 8:49 ` [PATCH 3/3] mac80211: allow configuring smps_mode_in_ps Johannes Berg
2013-10-01 10:17 ` Johannes Berg
2013-10-01 10:16 ` Johannes Berg [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=1380622603.14430.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox