[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180820025356.GF19200@thunk.org>
Date: Sun, 19 Aug 2018 22:53:56 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: Adam Borowski <kilobyte@...band.pl>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warnings from Linus' tree
On Mon, Aug 20, 2018 at 03:33:19AM +0200, Adam Borowski wrote:
> Valid uses of strncpy() do exist (such as SCSI structs), but those deal with
> fixed-width fields. Thus, gcc is right for warning for at least some of
> misuse of strncpy() for C strings. The function wasn't designed for them.
The problem is that the kernel has a goodly share of fixed-width
fields. The ext4 superblock is one of them. strncpy() is the most
convenient function to do what is needed. If it's a valid use, then
we need to have a way to get gcc to shut up about them.
- Ted
Powered by blists - more mailing lists