All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+cicac5bcbb130791ad@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: fscrypt: Remove FSCRYPT_MODE_MAX
Date: Thu, 18 Jun 2026 17:27:02 -0700	[thread overview]
Message-ID: <6a348cd6.d85dbdf7.1299fc.000c.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] fscrypt: Remove FSCRYPT_MODE_MAX
https://lore.kernel.org/all/20260618231404.132829-1-ebiggers@kernel.org
* [PATCH] fscrypt: Remove FSCRYPT_MODE_MAX

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/697a5bf7-8eeb-4ac3-9a44-8d3e149c87fa

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      9e7e6633458362db72427b48effad8d759131c35
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/d827beb4-174a-4b17-8f2d-2cefbdee4dfc/config

fs/crypto/fscrypt_private.h:635:45: error: use of undeclared identifier 'FSCRYPT_MODE_MAX'
fs/crypto/fscrypt_private.h:636:53: error: use of undeclared identifier 'FSCRYPT_MODE_MAX'
fs/crypto/fscrypt_private.h:637:53: error: use of undeclared identifier 'FSCRYPT_MODE_MAX'

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
  Tested-by: syzbot@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[ebiggers@kernel.org linux-fscrypt@vger.kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-06-19  0:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6a348cd6.d85dbdf7.1299fc.000c.GAE@google.com \
    --to=syzbot+cicac5bcbb130791ad@syzkaller.appspotmail.com \
    --cc=syzbot@lists.linux.dev \
    --cc=syzkaller-upstream-moderation@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.