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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20140925155252.GA5720@infradead.org>
Date:	Thu, 25 Sep 2014 08:52:52 -0700
From:	Christoph Hellwig <hch@...radead.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: enable sparse endianess checking by default?

It's been quite a while that we had sparse support in the build system,
and we still disable the checks for endianess annotations by default.

For many subsystems these are arguably the most useful ones, and with
Fengguang's build bot running sparse checks we're also being harder
on driver maintainers to sort these out even where they don't matter
too much for them (e.g. PCI hardware that mostly runs on x86).

Is there any reason to still keep the opt-in for these when running
sparse?

Now running sparse by default if available would be another useful
project, but I'll save that for a later time..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ