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]
Date:	Thu, 24 Jun 2010 15:46:09 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Borislav Petkov <bp@...64.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Huang Ying <ying.huang@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Borislav Petkov <petkovbb@...glemail.com>,
	linux-kernel@...r.kernel.org, mauro@...e.hu
Subject: Re: [RFC][PATCH] irq_work


* Andi Kleen <andi@...stfloor.org> wrote:

> > If its a critical error you do all the handling in the kernel and you
> 
> I assume you mean in MCE.  And the answer is no.
> 
> MCE generally can only panic or log, everything else
> needs other contexts.
> 
> > don't need task context at all, no? 
> 
> Process context is needed for various recovery schemes, all
> that need to sleep for example.

Please, as Peter and Boris asked you already, quote a concrete, specific 
example:

  'Specific event X occurs, kernel wants/needs to do Y. This cannot be done
   via the suggested method due to Z.'

Your generic arguments look wrong (to the extent they are specified) and it 
makes it much easier and faster to address your points if you dont blur them 
by vagaries.

Thanks,

	Ingo
--
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