linux-kernel - Re: [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <466E32C5.70105@aladin.ro>
Date:	Tue, 12 Jun 2007 08:44:37 +0300
From:	Eduard-Gabriel Munteanu <maxdamage@...din.ro>
To:	Jeff Dike <jdike@...toit.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] UML: fix missing non-blocking I/O, now DEBUG_SHIRQ
 works

*This message was transferred with a trial version of CommuniGate(r) Pro*
Jeff Dike wrote:
> No it won't.  UML builds without warnings here on x86_64.

Okay, I don't have an x86_64, sparc64 or something similar, as my 
computer is an x86, so I can't contradict this. If everything is fine on 
such arches, no fix is needed when nothing's broken... though I still 
think it's kind of ugly (though it's somehow ingenious as a hack) :)

Do you want me to resubmit the patch without these changes? I'll be back 
in a few hours (got to go now) and trim this out from the patch if 
that's necessary.
-
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/