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-next>] [day] [month] [year] [list]
Message-ID: <20190729220720.GB5712@roeck-us.net>
Date:   Mon, 29 Jul 2019 15:07:20 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     linux-watchdog@...r.kernel.org
Cc:     Arnd Bergmann <arnd@...db.de>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        linux-kernel@...r.kernel.org
Subject: Marking legacy watchdog drivers as deprecated / obsolete

Hi,

we have recently seen a number of changes to legacy watchdog drivers,
mostly surrounding the coding style used some 10+ years ago, but also
fixing minor formatting or coding problems found by static analyzers.
This slowly rises above the level of background noise.

Would it be acceptable to mark all those drivers as deprecated/obsolete,
warn users that the driver should be converted to use the watchdog
subsystem, and that it will otherwise be removed in a later Linux kernel
version ? This would give us an idea which drivers are still in use,
and it would enable us to remove the remaining drivers maybe 5 or 6
releases for now.

Thoughts ?

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ