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]
Message-ID: <180574a2-ec2f-cbe0-3458-02b5228db51e@web.de>
Date:   Mon, 16 Dec 2019 10:50:45 +0100
From:   Markus Elfring <Markus.Elfring@....de>
To:     Aditya Pakki <pakki001@....edu>, linux-wireless@...r.kernel.org,
        netdev@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        "David S. Miller" <davem@...emloft.net>,
        Kalle Valo <kvalo@...eaurora.org>, Kangjie Lu <kjlu@....edu>
Subject: Re: [PATCH] orinoco: avoid assertion in case of NULL pointer

> The patch replaces the BUG_ON call to error return.

Would a wording like “Replace the BUG_ON() call by a return of an error code
after a null pointer check” be nicer for this change description?

Will the tag “Fixes” become helpful here?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ