From: Coly Li <colyli@suse.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
linux-bcache@vger.kernel.org
Subject: Re: [PATCH] bcache: Use scnprintf() for avoiding potential buffer overflow
Date: Fri, 20 Mar 2020 00:32:33 +0800 [thread overview]
Message-ID: <343532cd-1354-913b-e0d0-8e323147c1a4@suse.de> (raw)
In-Reply-To: <s5hsgi4tikr.wl-tiwai@suse.de>
On 2020/3/20 12:28 上午, Takashi Iwai wrote:
> On Thu, 19 Mar 2020 17:27:47 +0100,
> Coly Li wrote:
>>
>> On 2020/3/19 11:58 下午, Takashi Iwai wrote:
>>> On Wed, 11 Mar 2020 08:45:58 +0100,
>>> Takashi Iwai wrote:
>>>>
>>>> Since snprintf() returns the would-be-output size instead of the
>>>> actual output size, the succeeding calls may go beyond the given
>>>> buffer limit. Fix it by replacing with scnprintf().
>>>>
>>>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>>>
>>> A gentle reminder for this forgotten patch.
>>> Let me know if any further changes are needed.
>>>
>>
>> Hi Takashi,
>>
>> This is in my for-next list already. Sorry for not reply you yet, just
>> busy on the testing with combined with md raid backend.
>
> OK, thanks. I just wondered because it didn't appear on linux-next,
> either.
I don't submit the patch set to Jens yet, because my local testing not
finished yet. Hopefully it may finish in next 2 days.
--
Coly Li
prev parent reply other threads:[~2020-03-19 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 7:45 [PATCH] bcache: Use scnprintf() for avoiding potential buffer overflow Takashi Iwai
2020-03-19 15:58 ` Takashi Iwai
2020-03-19 16:27 ` Coly Li
2020-03-19 16:28 ` Takashi Iwai
2020-03-19 16:32 ` Coly Li [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=343532cd-1354-913b-e0d0-8e323147c1a4@suse.de \
--to=colyli@suse.de \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--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