Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1510762
| From | Alexander Potapenko <glider@google.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next: build warning in Linus' tree |
| Date | 2016-10-28 01:10 +0200 |
| Message-ID | <sx1Y5-8mn-9@gated-at.bofh.it> (permalink) |
| References | <sx1ln-7TN-5@gated-at.bofh.it> <sx1EK-80D-9@gated-at.bofh.it> <sx1Y5-8mn-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Oct 27, 2016 at 4:01 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > On Thu, Oct 27, 2016 at 3:48 PM, Linus Torvalds > <torvalds@linux-foundation.org> wrote: >> >> I wonder if we should make KASAN depend on !COMPILE_TEST, because it >> does seem to disable a lot of build-time testing. > > Actually, we should probably just make the MEMORY_HOTPLUG dependency be > > depends on COMPILE_TEST || !KASAN Maybe we could just reverse the MEMORY_HOTPLUG->!KASAN dependency to make it KASAN->!MEMORY_HOTPLUG? Is it at all correct that allmodconfig enables KASAN? If/when we have other compiler-based tools, which of them will allmodconfig pick? > since the memory-hotplug code should still *build* with KASAN, it just > doesn't work. That's exactly what the COMPILE_TEST config option is > there for - to get build coverage even for things that aren't > necessarily sane to run. > > I'll do that, to get my build coverage up. I really expected my > allmodconfig builds to verify that I had removed the per-zone > waitqueue code completely, and I'm happy that the breakage was > apparently limited to that unused variable.. > > In the meantime, thanks for noticing and letting me know. > > Linus -- Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Straße, 33 80636 München Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
linux-next: build warning in Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-10-28 00:30 +0200
Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 00:50 +0200
Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 01:10 +0200
Re: linux-next: build warning in Linus' tree Alexander Potapenko <glider@google.com> - 2016-10-28 01:10 +0200
Re: linux-next: build warning in Linus' tree Linus Torvalds <torvalds@linux-foundation.org> - 2016-10-28 01:30 +0200
Re: linux-next: build warning in Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-10-28 01:50 +0200
Re: linux-next: build warning in Linus' tree Geert Uytterhoeven <geert@linux-m68k.org> - 2016-10-29 23:30 +0200
csiph-web