linux-kernel - Re: A question about state machine function state

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: <20150601120103.GF20384@8bytes.org>
Date:	Mon, 1 Jun 2015 14:01:03 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Baoquan He <bhe@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: A question about state machine function state_next()

On Mon, Jun 01, 2015 at 07:18:02PM +0800, Baoquan He wrote:
> Checked the code again, it may be a code bug if this is done in
> device_dma_ops_init(). Since this is called in
> amd_iommu_init_dma_ops()<-amd_iommu_init_dma(). And amd_iommu_init_dma()
> is only called in case IOMMU_INTERRUPTS_EN code block. According to the
> code flow if I understand correctly, it can't be here at boot stage.
> state_next() will change the state according to the calling times. And
> in amd iommu only four times to call iommu_go_to_state, it can't go to
> IOMMU_PCI_INIT and the after cases.
> 
> I am not sure if my understanding is correct, or I missed something.

You probably missed the loop in iommu_go_to_state() which will call
state_next() until it reaches either the requested state or an error
state.


	Joerg

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