Subject: Re: [PATCH] rwlock_is_locked undefined for UP systems
From: Arjan van de Ven <arjanv@redhat.com>
Reply-To: arjanv@redhat.com
To: Prashanth T <prasht@in.ibm.com>
Cc: rml@tech9.net, linux-kernel@vger.kernel.org
In-Reply-To: <4007EAE7.2030104@in.ibm.com>
References: <4007EAE7.2030104@in.ibm.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-L+r5ouUt+J1LLFEK0t3V"
Organization: Red Hat, Inc.
Message-Id: <1074261350.4434.4.camel@laptop.fenrus.com>
Mime-Version: 1.0
Date: Fri, 16 Jan 2004 14:55:50 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1158
Lines: 35


--=-L+r5ouUt+J1LLFEK0t3V
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2004-01-16 at 14:45, Prashanth T wrote:
> Hi,
>     I had to use rwlock_is_locked( ) with linux2.6 for kdb and noticed th=
at
> this routine to be undefined for UP.  I have attached the patch for 2.6.1
> below to return 0 for rwlock_is_locked( ) on UP systems.
> Please let me know.

I consider any user of this on UP to be broken, just like UP use of
spin_is_locked() is always a bug..... better a compiletime bug than a
runtime bug I guess...

--=-L+r5ouUt+J1LLFEK0t3V
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAB+1mxULwo51rQBIRAkQsAKCbm1wBePb6l6iXKXKMaZYfDQtkawCfSrSX
LyneYLI7SZJIhbcYLH16rM4=
=T1cl
-----END PGP SIGNATURE-----

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