linux-kernel - Re: [PATCH 2/3] iommu/vt-d: Parse SATC reporting structure

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:   Tue, 2 Feb 2021 14:53:05 +0100
From:   Joerg Roedel <joro@...tes.org>
To:     Lu Baolu <baolu.lu@...ux.intel.com>
Cc:     iommu@...ts.linux-foundation.org, Yian Chen <yian.chen@...el.com>,
        Ashok Raj <ashok.raj@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] iommu/vt-d: Parse SATC reporting structure

On Tue, Feb 02, 2021 at 12:40:56PM +0800, Lu Baolu wrote:
> +	case ACPI_DMAR_TYPE_SATC:
> +		satc = container_of(header, struct acpi_dmar_satc, header);
> +		pr_info("SATC flags: 0x%x\n", satc->flags);
> +		break;

Did the pr_info() slip through or is there a real purpose for having
this information in the kernel log?