[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdc0dbee0f60823ccc6a5cd0a25a8242dd94c215.camel@perches.com>
Date: Fri, 27 Aug 2021 12:08:28 -0700
From: Joe Perches <joe@...ches.com>
To: Borislav Petkov <bp@...en8.de>, Len Baker <len.baker@....com>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>,
Tony Luck <tony.luck@...el.com>,
James Morse <james.morse@....com>,
Robert Richter <rric@...nel.org>,
David Laight <David.Laight@...lab.com>,
Kees Cook <keescook@...omium.org>,
linux-hardening@...r.kernel.org, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] EDAC/mc: Prefer strscpy over strcpy
On Fri, 2021-08-27 at 19:54 +0200, Borislav Petkov wrote:
> So it would be a lot more robust if something would catch that change,
> albeit seemingly redundant now.
I still think scnprintf is _way_ more common and intelligible as
a construct than this odd strscpy with required error checking.
Powered by blists - more mailing lists