linux-kernel - RE: Bitops source problem

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

Message-ID: <1145971D427D7F43B0DBDAE22221C4B5035FDDAE@nipns00a210.FPS.NIHILENT.COM>
Date:	Fri, 18 Jan 2008 10:10:11 +0530
From:	"Pravin Nanaware" <p.nanaware@...ilent.com>
To:	"Roland Dreier" <rdreier@...co.com>
Cc:	"John Hubbard" <john.hubbard@...il.com>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: RE: Bitops source problem

I have a CentOS 4.4 system with 2.6.9-42 kernel. I will update the kernel to the new one. 

Regards,
Pravin


-----Original Message-----
From: Roland Dreier [mailto:rdreier@...co.com]
Sent: Friday, January 18, 2008 1:03 AM
To: Pravin Nanaware
Cc: John Hubbard; LKML
Subject: Re: Bitops source problem


 > Yes, indeed none of the atomic bit operations functions has
 > LOCK_PREFIX in my version of Linux kernel.

You have a broken source tree then.  Where did your kernel source come
from then?  I'm not able to find any version of asm-i386/bitops.h
where clear_bit() doesn't have LOCK_PREFIX in any of the trees I
happen to have lying around  (which includes some very old trees like 2.4.21)

 - R.

-**************Nihilent***************
" *** All information contained in this communication is confidential, proprietary, privileged
and is intended for the addressees only. If youhave received this E-mail in error please notify
mail administrator by telephone on +91-20-39846100 or E-mail the sender by replying to
this message, and then delete this E-mail and other copies of it from your computer system.
Any unauthorized dissemination,publication, transfer or use of the contents of this communication,
with or without modifications is punishable under the relevant law.

Nihilent has scanned this mail with current virus checking technologies. However, Nihilent makes no 
representations or warranties to the effect that this communication is virus-free.

Nihilent reserves the right to monitor all E-mail communications through its Corporate Network. *** "

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