From: frezidok1@gmail.com
To: yocto-patches@lists.yoctoproject.org
Cc: Dmitry Sakhonchik <frezidok1@gmail.com>
Subject: [pseudo] [PATCH v2 0/4] Add open_tree() wrapper
Date: Fri, 4 Sep 2026 16:06:23 +0300 [thread overview]
Message-ID: <20260904130627.453678-1-frezidok1@gmail.com> (raw)
From: Dmitry Sakhonchik <frezidok1@gmail.com>
v2:
- Handle relative paths correctly in the open_tree wrapper
- Add fallback to SYS_open_tree when libc function is absent
- Add tests coverage with relative paths (dirfd != AT_FDCWD)
- Add support and tests for syscall(SYS_open_tree, ...)
Dmitry Sakhonchik (4):
ports/linux/guts: Add open_tree wrapper
test: Add open_tree test
ports/linux/pseudo_wrappers.c: Add syscall support for open_tree()
wrapper
test: Add open_tree syscall test
ports/linux/guts/open_tree.c | 46 ++++++++++
ports/linux/portdefs.h | 9 ++
ports/linux/pseudo_wrappers.c | 14 +++
ports/linux/wrapfuncs.in | 1 +
test/test-open_tree-syscall.c | 152 +++++++++++++++++++++++++++++++++
test/test-open_tree-syscall.sh | 5 ++
test/test-open_tree.c | 139 ++++++++++++++++++++++++++++++
test/test-open_tree.sh | 5 ++
8 files changed, 371 insertions(+)
create mode 100644 ports/linux/guts/open_tree.c
create mode 100644 test/test-open_tree-syscall.c
create mode 100755 test/test-open_tree-syscall.sh
create mode 100644 test/test-open_tree.c
create mode 100755 test/test-open_tree.sh
next reply other threads:[~2026-09-04 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:06 frezidok1 [this message]
2026-09-04 13:06 ` [pseudo] [PATCH v2 1/4] ports/linux/guts: Add open_tree wrapper frezidok1
2026-09-04 13:06 ` [pseudo] [PATCH v2 2/4] test: Add open_tree test frezidok1
2026-09-04 13:06 ` [pseudo] [PATCH v2 3/4] ports/linux/pseudo_wrappers.c: Add syscall support for open_tree() wrapper frezidok1
2026-09-04 13:06 ` [pseudo] [PATCH v2 4/4] test: Add open_tree syscall test frezidok1
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=20260904130627.453678-1-frezidok1@gmail.com \
--to=frezidok1@gmail.com \
--cc=yocto-patches@lists.yoctoproject.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 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.