From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: Please apply commit ebe559609d78 ("fs: get rid of __FMODE_NONOTIFY kludge") to v6.12.y
Date: Thu, 22 Oct 2026 09:02:15 +0200 [thread overview]
Message-ID: <2026102206-trinity-feminism-b082@gregkh> (raw)
In-Reply-To: <7701ab76-4761-4596-b6a5-92c74e03ce5f@roeck-us.net>
On Wed, Oct 21, 2026 at 02:50:08PM -0700, Guenter Roeck wrote:
> Hi,
>
> all sparc32 and sparc64 builds in v6.12.y fail as follows.
>
> Building sparc32:defconfig ... failed
> --------------
> Error log:
> <stdin>:1519:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> kernel/fork.c: In function '__do_sys_clone3':
> kernel/fork.c:3114:2: warning: #warning clone3() entry point is missing, please fix [-Wcpp]
> 3114 | #warning clone3() entry point is missing, please fix
> | ^~~~~~~
> In file included from <command-line>:
> fs/fcntl.c: In function 'fcntl_init':
> include/linux/compiler_types.h:543:45: error: call to '__compiletime_assert_325' declared with attribute error: BUILD_BUG_ON failed: 21 - 1 != HWEIGHT32( (VALID_OPEN_FLAGS & ~(O_NONBLOCK | O_NDELAY)) | __FMODE_EXEC | __FMODE_NONOTIFY)
> 543 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>
> Bisect points to commit 07ee6057f92a ("fsnotify: opt-in for permission events
> at file open time"). See bisect log below for reference.
>
> Please apply commit ebe559609d78 ("fs: get rid of __FMODE_NONOTIFY kludge")
> to v6.12.y to fix the problem (assuming there is interest in sparc builds
> on v6.12.y kernels - this has been broken since v6.12.105).
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2026-10-22 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 21:50 Please apply commit ebe559609d78 ("fs: get rid of __FMODE_NONOTIFY kludge") to v6.12.y Guenter Roeck
2026-10-22 7:02 ` Greg Kroah-Hartman [this message]
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=2026102206-trinity-feminism-b082@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=sashal@kernel.org \
--cc=stable@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