linux-kernel - Re: kexec reboot broken with ioatdma?

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, 17 Dec 2009 10:45:29 +1100
From:	Simon Horman <horms@...ge.net.au>
To:	Roland Dreier <rdreier@...co.com>
Cc:	linux-kernel@...r.kernel.org,
	Dan Williams <dan.j.williams@...el.com>,
	kexec@...ts.infradead.org
Subject: Re: kexec reboot broken with ioatdma?

On Wed, Dec 16, 2009 at 03:42:20PM -0800, Roland Dreier wrote:
> 
>  > If its reset in a standard path, then yes that seems sensible to me.
>  > I'm mainly concerned about avoiding something along the lines of:
>  > 
>  > 	if (is_booting_from_kexec)
>  > 		reset_hw();
> 
> I think we all agree... the idea is to change from
> 
> 	init_hw()
> 	{
> 		/* assume hw is in pristine state */
> 		do_init();
> 	}
> 
> to
> 
> 	init_hw()
> 	{
> 		/* hw is in unknown state */
> 		reset_hw();
> 		do_init();
> 	}
> 
>  - R.

Yes, I think we all agree :-)

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