lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 16 Aug 2020 19:17:56 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jeff Layton <jlayton@...hat.com>
Subject: Re: Linux 5.9-rc1 (sparse? kernel/time/timekeeping.c)

On 8/16/20 7:15 PM, Luc Van Oostenryck wrote:
> On Sun, Aug 16, 2020 at 06:35:26PM -0700, Randy Dunlap wrote:
>>
>> on x86_64, allmodconfig:
>>
>> $ gcc --version
>> gcc (SUSE Linux) 7.5.0
>>
>> $ sparse --version
>> 0.6.2
>>
>>
>> I seem to be having some problems with kernel/time/timekeeping.c,
>> including a segfault.
>>
>> a. Is it sparse that segfaults?
> 
> It's most probably the one fixed in:
>   eb6779f6f621 ("generic: fix missing inlining of generic expression")
> 
> On the main tree there is a branch with a few fixes since the last release:
>   git://git.kernel.org/pub/scm/devel/sparse/sparse.git maint-v0.6.2
>  
>> b. what prints this message?
>> make[3]: *** Deleting file 'kernel/time/timekeeping.o'
> 
> It seems like a typical message from make when a command fails.
>  
>> c. I would prefer to be able to tell the source of warning/error messages,
>> i.e., gcc or sparse. Especially when they are intermixed.
> 
> You can use the option -fdiagnostic-prefix[=PREFIX] for this. It will
> just prefix all messages from from sparse with the given PREFIX or
> 'sparse: ' if none is given. You can pass this option via 'make CF=...'.
> 
> It may be a good idea to directly add it to CHECKFLAGS.
> 
> Best regards,
> -- Luc

Thank you, Luc.  I'll get the latest and also use PREFIX.


-- 
~Randy

Powered by blists - more mailing lists