On Fri, Aug 30, 2019 at 12:46:21PM -0700, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Fri, Aug 30, 2019 at 12:42 PM 'Nick Desaulniers' via syzkaller-bugs > <syzkaller-bugs@xxxxxxxxxxxxxxxx> wrote: > > > > Dmitry, > > Any idea how clang-built-linux got CC'ed on this? Is syzcaller > > running clang builds, yet? (this looks like a GCC build) > > syzbot always uses get_maintainers: > > $ ./scripts/get_maintainer.pl -f fs/ext4/super.c > "Theodore Ts'o" <tytso@xxxxxxx> (maintainer:EXT4 FILE SYSTEM) > Andreas Dilger <adilger.kernel@xxxxxxxxx> (maintainer:EXT4 FILE SYSTEM) > linux-ext4@xxxxxxxxxxxxxxx (open list:EXT4 FILE SYSTEM) > linux-kernel@xxxxxxxxxxxxxxx (open list) > clang-built-linux@xxxxxxxxxxxxxxxx (open list:CLANG/LLVM BUILD SUPPORT) > CLANG/LLVM BUILD SUPPORT L: clang-built-linux@xxxxxxxxxxxxxxxx W: https://clangbuiltlinux.github.io/ B: https://github.com/ClangBuiltLinux/linux/issues C: irc://chat.freenode.net/clangbuiltlinux S: Supported K: \b(?i:clang|llvm)\b So, clang-built-linux has volunteered to maintain every file that contains the word "clang" or "llvm" anywhere in its contents :-) $ grep clang fs/ext4/super.c (void) ei; /* shut up clang warning if !CONFIG_LOCKDEP */ - Eric
