From: syzbot ci <syzbot+cifba781775c24e678@syzkaller.appspotmail.com>
To: jkoolstra@xs4all.nl, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzbot@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: vfs: add O_CREAT|O_DIRECTORY to open*(2)
Date: Mon, 25 May 2026 04:39:25 -0700 [thread overview]
Message-ID: <6a1434ed.170a0220.22ae77.0005.GAE@google.com> (raw)
In-Reply-To: <1931576426.2416655.1779705327168@kpc.webmail.kpnmail.nl>
syzbot ci has tested the suggested fix patch on top of the following series:
[v4] vfs: add O_CREAT|O_DIRECTORY to open*(2)
https://lore.kernel.org/all/20260518165237.2084042-1-jkoolstra@xs4all.nl
Patch: https://ci.syzbot.org/jobs/3effa8d6-6f06-49b5-b228-7c7502ca630d/patch
The patch testing request could not be completed:
Testing failed due to an infrastructure error.
Testing results:
* [build 0] Build Patched: error
Full report is available here:
https://ci.syzbot.org/session/e7a8e9a6-6522-439a-a09c-39da7d9d738b
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2026-05-25 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 16:52 [RFC PATCH v4 0/2] vfs: add O_CREAT|O_DIRECTORY to open*(2) Jori Koolstra
2026-05-18 16:52 ` [RFC PATCH v4 1/2] " Jori Koolstra
2026-05-18 16:52 ` [RFC PATCH v4 2/2] selftest: add tests for open*(O_CREAT|O_DIRECTORY) Jori Koolstra
2026-05-19 6:59 ` [syzbot ci] Re: vfs: add O_CREAT|O_DIRECTORY to open*(2) syzbot ci
2026-05-25 10:35 ` Jori Koolstra
2026-05-25 11:39 ` syzbot ci [this message]
2026-05-25 18:30 ` Jori Koolstra
2026-05-25 19:02 ` syzbot ci
-- strict thread matches above, loose matches on Subject: below --
2026-05-17 17:02 [RFC PATCH v3 0/2] " Jori Koolstra
2026-05-18 7:28 ` [syzbot ci] " syzbot ci
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=6a1434ed.170a0220.22ae77.0005.GAE@google.com \
--to=syzbot+cifba781775c24e678@syzkaller.appspotmail.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox