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] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e47b106-12d7-908a-857f-3908336f2e1f@acm.org>
Date:   Wed, 25 Sep 2019 18:33:35 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     Daniel Wagner <dwagner@...e.de>, qla2xxx-upstream@...gic.com
Cc:     linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Himanshu Madhani <hmadhani@...vell.com>
Subject: Re: WARN_ON_ONCE in qla2x00_status_cont_entry

On 2019-09-25 05:39, Daniel Wagner wrote:
> So I after starring on the code I am not sure if the WARN_ON_ONCE is
> correct. It assumes that after processing one status continuation,
> there is no more work. Though it looks like there is another element
> to process. Is it possible that two sense continuation are possible?

According to the firmware documentation it is possible that multiple
status continuations are emitted by the firmware. Do you want to submit
a patch or do you prefer that I do this myself?

Thanks,

Bart.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ