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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0901091432270.3525@asgard.lang.hm>
Date:	Fri, 9 Jan 2009 14:33:08 -0800 (PST)
From:	david@...g.hm
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Partially defer some of the async stuff to the next release

On Fri, 9 Jan 2009, Alan Cox wrote:

>> Can we rather make this something that people can enable with a "fastboot"
>> option and is disabled by default? At least that way the ATA people can
>> see the problem, and don't just forget about it, since we want it fixed.
>
> Makes some sense - although the inode one should just take a hike at this
> point. Can the fastboot option live under staging perhaps - its analogous
> to staging drivers although clearly the code doesn't go there in this
> case ?
>
> The trouble otherwise is "fast boot" sounds like something good for
> people to turn on, but right now it's the reverse.

isn't this like OPTIMIZE_INLINE?

David Lang
--
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