linux-kernel - Re: drbd_worker.c: Remove lines

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]

Message-ID: <1406016591.23999.40.camel@marge.simpson.net>
Date:	Tue, 22 Jul 2014 10:09:51 +0200
From:	Mike Galbraith <umgwanakikbuti@...il.com>
To:	Nick Krause <xerofoify@...il.com>
Cc:	drbd-dev@...ts.linbit.com, drbd-user@...ts.linbit.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: drbd_worker.c: Remove lines

On Tue, 2014-07-22 at 02:17 -0400, Nick Krause wrote: 
> There seems to be two fix mes in function in wait_for_work. I was
> wondering can we remove these spinlocks?

Rather than ask someone else this question, take a look to see what the
lock protects and from whom.  If protected thingy cannot possibly be
diddled concurrently, you'll know what to do, if it can be, you'll know
what to do.  If you can't figure it out, move on to the next windmill
until the last one on the planet has been tilted or bounced off of :)

-Mike

--
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/