mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Memory Management List <linux-mm@kvack.org>
Cc: Jeff Xu <jeffxu@google.com>,
	Daniel Verkamp <dverkamp@chromium.org>,
	Kees Cook <keescook@chromium.org>,
	David Herrmann <dh.herrmann@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Hugh Dickins <hughd@google.com>, Jann Horn <jannh@google.com>,
	Jorge Lucangeli Obes <jorgelo@chromium.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stuart Foster <smf-linux@virginmedia.com>
Subject: Fwd: Started to get "memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL"
Date: Thu, 1 Jun 2023 09:07:20 +0700	[thread overview]
Message-ID: <69dad53e-9363-c551-111a-d0051bb0265f@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> Recent kernels seem to generate this:
> 
> "memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=3976 'Xorg'"
> 
> Is this a kernel problem or something to do with Xorg ?
> 
> Seen in Kernels 6.3.4 and 6.4.0-rc4.
> 
> Thanks

See Bugzilla for the full thread and attached logs (dmesg, xorg, bisection
log).

Anyway, I'm adding it to regzbot:

#regzbot introduced: 105ff5339f498a https://bugzilla.kernel.org/show_bug.cgi?id=217508
#regzbot title: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL on Xorg

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217508

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-06-01  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  2:07 Bagas Sanjaya [this message]
2023-06-01  7:18 ` Vlastimil Babka
2023-06-01 14:12   ` Kees Cook
2023-06-02  2:15     ` Bagas Sanjaya
2023-06-02  7:12       ` Stuart Foster

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=69dad53e-9363-c551-111a-d0051bb0265f@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dh.herrmann@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dverkamp@chromium.org \
    --cc=hughd@google.com \
    --cc=jannh@google.com \
    --cc=jeffxu@google.com \
    --cc=jorgelo@chromium.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=regressions@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=smf-linux@virginmedia.com \
    /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
all inboxes | Powered by JetHome®