Re: kcsan -Wmaybe-uninitialized warning in ntfs3
Marco Elver <[email protected]> Wed, 22 Apr 2026 10:23:40 +0200
| Newsgroups | dev.linux.lists.ntfs3,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CANpmjNN8J=cFnsQpj+_VXuoswsc500jRV=mKDBSntZw0Xvib4w@mail.gmail.com> |
On Wed, 22 Apr 2026 at 10:00, Arnd Bergmann <[email protected]> wrote: > > On Tue, Apr 21, 2026, at 21:12, Arnd Bergmann wrote: > > On Tue, Apr 21, 2026, at 21:06, Marco Elver wrote: > >> On Tue, 21 Apr 2026 at 17:26, Marco Elver <[email protected]> wrote: > >> [...] > >>> > To me, 2 makes more sense. The attribute requires gcc-11 or higher, > >>> > so you need to wrap that in a compiler version specific macro, > >>> > but since I only saw the warning with gcc-12 and higher, that > >>> > should be fine. > >> > >> Kindly test if you can: > >> https://lore.kernel.org/all/[email protected]/ > > > > Applied to my randconfig tree and verified that this fixes the > > known warning (only one out of about 200 random configs). I'll > > let you know if something comes up by tomorrow. > > Unfortunately, there are new warnings after your patches using > gcc-11. In 500 randconfig builds with that compiler, I saw 7 > configurations failing with one of these four messages: Looks like a compiler bug to me; can you check gcc-12+ ? Maybe we need to allow the __access attribute only for later GCC versions.