linux-kernel - Re: [PATCH 1/1] semaphore: declare down

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] [day] [month] [year] [list]

Message-Id: <20080730094817.135cdbfa.akpm@linux-foundation.org>
Date:	Wed, 30 Jul 2008 09:48:17 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	linux-kernel@...r.kernel.org, xsonnek@...il.com,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 1/1] semaphore: declare down_try

On Wed, 30 Jul 2008 13:27:36 +0200 Jiri Slaby <jirislaby@...il.com> wrote:

> Jiri Slaby napsal(a):
> > Maybe you already fixed this, in todays mmotm there is a fix of duplicate
> > down_try definiton, but this problem still persist.
> 
> BTW. there is still bunch of down_trylock(); users, are you about to 
> eliminate them?
> 
>     2    182  /home/latest/xxx/drivers/watchdog/ar7_wdt.c <<ar7_wdt_open>>
>               if (down_trylock(&open_semaphore))
>     3    309  /home/latest/xxx/drivers/watchdog/it8712f_wdt.c
>               <<it8712f_wdt_open>>
>               if (down_trylock(&it8712f_wdt_sem))
>     4    214  /home/latest/xxx/drivers/watchdog/s3c2410_wdt.c
>               <<s3c2410wdt_open>>
>               if(down_trylock(&open_lock))
>     5    154  /home/latest/xxx/drivers/watchdog/sc1200wdt.c <<sc1200wdt_open>>
>               if (down_trylock(&open_sem))
>     6     95  /home/latest/xxx/drivers/watchdog/scx200_wdt.c <<scx200_wdt_open>>
>               if (down_trylock(&open_semaphore))
>     7    429  /home/latest/xxx/drivers/watchdog/wdt_pci.c <<wdtpci_open>>
>               if (down_trylock(&open_sem))

oh crap, yes, sorry, I had a bit of a catastrophe with two different
versions of the sameish thing coming from two directions and my
approach to fixing that was to drop one patch and to await the next
linux-next pull for the other.  Forgot.
--
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/