[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3b63d8d9-4246-3010-49e9-fbc433b1ce36@suse.de>
Date: Mon, 31 Jul 2023 18:17:49 +0200
From: Hannes Reinecke <hare@...e.de>
To: Christoph Hellwig <hch@....de>, Mark O'Donovan <shiftee@...teo.net>
Cc: linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
sagi@...mberg.me, axboe@...nel.dk, kbusch@...nel.org
Subject: Re: [PATCH 2/2] nvme-auth: set explanation code for failure2 msgs
On 7/31/23 07:58, Christoph Hellwig wrote:
> On Thu, Jul 27, 2023 at 01:47:48PM +0000, Mark O'Donovan wrote:
>> These error cases were not setting an auth-failure-reason-code-explanation.
>> This means an AUTH_Failure2 message will be sent with an explanation value
>> of 0 which is a reserved value.
>
> I'll leave the final decision to Hannes, but shouldn't we find a common
> place, either behind a label or in the body of the function to set
> chap->status? Having to add this in a lot of error labels doesn't feel
> very maintainable.
>
Yeah; the whole AUTH_XXX errors are ever so cumbersome as we don't have
a good way to passing them up the stack. Plus we can't transport errors
during connect, making it doubly pointless.
Maybe a printk() somewhere. I'll check.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
Powered by blists - more mailing lists