linux-kernel - Re: [Bugme-new] [Bug 7602] New: Failure on compilation: include/asm/bitops.h:122: error: inconsistent operand constraints in an `asm' in nfs_access_add

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

Date:	Thu, 30 Nov 2006 13:37:48 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Andi Kleen <ak@...e.de>
Cc:	bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org,
	mjw99@...ac.uk
Subject: Re: [Bugme-new] [Bug 7602] New: Failure on compilation:
 include/asm/bitops.h:122: error: inconsistent operand constraints in an
 `asm' in nfs_access_add_cache()

On Thu, 30 Nov 2006 13:18:53 -0800
bugme-daemon@...zilla.kernel.org wrote:

> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7602
> 
>            Summary: Failure on compilation: include/asm/bitops.h:122: error:
>                     inconsistent operand constraints in an `asm' in
>                     nfs_access_add_cache()
>     Kernel Version: 2.6.19
>             Status: NEW
>           Severity: high
>              Owner: trond.myklebust@....uio.no
>          Submitter: mjw99@...ac.uk
> 
> 
> Most recent kernel where this bug did *NOT* occur: 
> 2.6.18.3
> 
> Distribution: 
> RHEL4-U2 AS
> 
> Hardware Environment:
> 8 CPU Dual Core Opteron box with 32Gb of ram 
> http://www.iwill.net/product_2.asp?p_id=90&sp=Y
> 
> Software Environment:
> RHEL4-U2
> gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
> 
> Problem Description:
> 
> Compilation fails with the error message:
> ....
>   CC      fs/nfs/client.o
>   CC      fs/nfs/dir.o
> fs/nfs/dir.c: In function `nfs_access_add_cache':
> include/asm/bitops.h:122: error: inconsistent operand constraints in an `asm'

Seems that this:

static __inline__ int __test_and_set_bit(int nr, volatile void * addr)
{
	int oldbit;

	__asm__(
		"btsl %2,%1\n\tsbbl %0,%0"
		:"=r" (oldbit),"+m" (ADDR)
		:"dIr" (nr));
	return oldbit;
}

explodes with gcc-3.4.4.


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