linux-kernel - Re: Build regressions/improvements in v3.0-rc5 (xfs on cris)

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

Date:	Thu, 30 Jun 2011 16:34:07 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	xfs-masters@....sgi.com,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-cris-kernel@...s.com
Subject: Re: Build regressions/improvements in v3.0-rc5 (xfs on cris)

On Thu, Jun 30, 2011 at 5:24 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Wed, Jun 29, 2011 at 02:21:06PM -0700, Randy Dunlap wrote:
>> Looks like arch/cris does not support atomic64_t.  (?)
>>
>> Should we prevent xfs from being built on arch/cris?
>
> Or nuke cris until it's able to at least include an asm-generic header?
>

Not that simple. Take a look at lib/atomic64_test.c, it said:

#if defined(CONFIG_X86) || defined(CONFIG_MIPS) || defined(CONFIG_PPC) || \
    defined(CONFIG_S390) || defined(_ASM_GENERIC_ATOMIC64_H) ||
defined(CONFIG_ARM)
...
#else
#warning Please implement atomic64_dec_if_positive for your
architecture, and add it to the IF above
#endif

So cris at least needs to implement atomic64_dec_if_positive()...
--
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/