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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Mon, 25 May 2020 15:34:47 +0200
From:   Markus Elfring <>
To:     Qiushi Wu <>
Cc:,,, "David S. Miller" <>,
        Jakub Kicinski <>, Kangjie Lu <>,
        Manish Chopra <>,
Subject: Re: [PATCH] qlcnic: Complete exception handling in

> …, function qlcnic_83xx_diag_alloc_res() is not handled by
> function qlcnic_83xx_diag_free_res() after a call of …

I have got understanding difficulties for this wording.

> Fix this issue by adding a jump target "fail_mbx_args",
> and jump to this new target when qlcnic_alloc_mbx_args() failed.

Would a wording variant like the following be more succinct?

  Thus add the jump target “fail_mbx_args” to complete the exception handling.


Powered by blists - more mailing lists