From: Matthew Wilcox <willy@infradead.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: bcachefs-for-review
Date: Thu, 5 Nov 2020 16:01:47 +0000 [thread overview]
Message-ID: <20201105160147.GO17076@casper.infradead.org> (raw)
In-Reply-To: <20201027200433.GA449905@moria.home.lan>
On Tue, Oct 27, 2020 at 04:04:33PM -0400, Kent Overstreet wrote:
> Here's where bcachefs is at and what I'd like to get merged:
>
> https://evilpiepirate.org/git/bcachefs.git/log/?h=bcachefs-for-review
When building for x86-32 (ie make allnoconfig, enable BLOCK, enable BCACHEFS):
../fs/bcachefs/util.h:40: warning: "memcpy" redefined
40 | #define memcpy(dst, src, len) \
../arch/x86/include/asm/string_32.h:182: note: this is the location of the previous definition
182 | #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
In function ‘journal_seq_copy’,
inlined from ‘__bch2_create’ at ../fs/bcachefs/fs.c:291:3:
../arch/x86/include/asm/cmpxchg.h:128:3: error: call to ‘__cmpxchg_wrong_size’ declared with attribute error: Bad argument size for cmpxchg
which comes from:
../fs/bcachefs/fs.c:52:16: note: in expansion of macro ‘cmpxchg’
52 | } while ((v = cmpxchg(&dst->ei_journal_seq, old, journal_seq)) != old);
... and similar problems elsewhere in fs.c.
next prev parent reply other threads:[~2020-11-05 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 20:04 bcachefs-for-review Kent Overstreet
2020-11-04 19:53 ` bcachefs-for-review Oleksandr Natalenko
2020-11-05 16:01 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 22:37 bcachefs-for-review Kent Overstreet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201105160147.GO17076@casper.infradead.org \
--to=willy@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).