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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <66a032df-d54f-471a-8219-5f41c2298b5f@amd.com>
Date: Fri, 21 Nov 2025 10:51:55 +0530
From: Sairaj Kodilkar <sarunkod@....com>
To: Jason Gunthorpe <jgg@...dia.com>
CC: Vasant Hegde <vasant.hegde@....com>, <iommu@...ts.linux.dev>,
	<linux-kernel@...r.kernel.org>, <joro@...tes.org>,
	<suravee.suthikulpanit@....com>, <ashish.kalra@....com>,
	<robin.murphy@....com>, <will@...nel.org>
Subject: Re: [PATCH 1/2] amd/iommu: Preserve domain ids inside the kdump
 kernel



On 11/20/2025 6:26 PM, Jason Gunthorpe wrote:
> On Thu, Nov 20, 2025 at 10:32:32AM +0530, Sairaj Kodilkar wrote:
>
>> No, its not atomic context. My intension was to ensure that the
>> memory allocation succeeds. But I am not sure if it's the most
>> appropriate choice for this scenario
> This is early boot, it won't fail either way. Use GFP_KERNEL because
> it is clearer

Sure, Thanks for suggestion

-Sairaj

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ