From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: Use scnprintf() for avoiding potential buffer overflow
Date: Thu, 19 Mar 2020 11:38:20 -0700 [thread overview]
Message-ID: <20200319183820.GA117496@google.com> (raw)
In-Reply-To: <s5himj0uyzy.wl-tiwai@suse.de>
On 03/19, Takashi Iwai wrote:
> On Thu, 12 Mar 2020 02:08:03 +0100,
> Chao Yu wrote:
> >
> > On 2020/3/11 17:33, 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>
> >
> > Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> Could you guys apply the patch through your tree, or should I take it?
Sorry, I merged. Thanks~ :)
>
>
> thanks,
>
> Takashi
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-03-19 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 9:33 [f2fs-dev] [PATCH] f2fs: Use scnprintf() for avoiding potential buffer overflow Takashi Iwai
2020-03-12 1:08 ` Chao Yu
2020-03-19 15:48 ` Takashi Iwai
2020-03-19 18:38 ` Jaegeuk Kim [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=20200319183820.GA117496@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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.