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]
Date:	Mon, 4 Aug 2008 09:45:07 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Paul Menage <menage@...gle.com>, linux-kernel@...r.kernel.org,
	Matthew Wilcox <matthew@....cx>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH] Introduce down_try() so we can move away from
 down_trylock()

>       down_trylock -> down_try in drivers/watchdog/ar7_wdt.c
>       down_trylock -> down_try in drivers/watchdog/it8712f_wdt.c
>       down_trylock -> down_try in drivers/watchdog/s3c2410_wdt.c
>       down_trylock -> down_try in drivers/watchdog/sc1200wdt.c
>       down_trylock -> down_try in drivers/watchdog/scx200_wdt.c
>       down_trylock -> down_try in drivers/watchdog/wdt_pci.c

I sent fixes for all of those to the watchdog maintainer in May. The
patches are still sitting with the maintainer. They all convert to proper
locking rather than sem abuse, clean up all the coding style and fix
numerous bugs plus remove BKL requirements.

Wim it appears is still trying to get real life stuff sorted out so I
think at this point we really need a new watchdog maintainer.

(See series of 57 patches "watchdog: Giant scrub" about 19th May)

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists