io_uring/xattr.c
Source file repositories/reference/linux-study-clean/io_uring/xattr.c
File Facts
- System
- Linux kernel
- Corpus path
io_uring/xattr.c- Extension
.c- Size
- 4629 bytes
- Lines
- 198
- Domain
- Kernel Services
- Bucket
- io_uring
- Inferred role
- Kernel Services: implementation source
- Status
- source implementation candidate
Why This File Exists
Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/errno.hlinux/fs.hlinux/file.hlinux/mm.hlinux/slab.hlinux/namei.hlinux/io_uring.hlinux/xattr.huapi/linux/io_uring.h../fs/internal.hio_uring.hxattr.h
Detected Declarations
struct io_xattrfunction io_xattr_cleanupfunction io_xattr_finishfunction __io_getxattr_prepfunction io_fgetxattr_prepfunction io_getxattr_prepfunction io_fgetxattrfunction io_getxattrfunction __io_setxattr_prepfunction io_setxattr_prepfunction io_fsetxattr_prepfunction io_fsetxattrfunction io_setxattr
Annotated Snippet
struct io_xattr {
struct file *file;
struct kernel_xattr_ctx ctx;
struct delayed_filename filename;
};
void io_xattr_cleanup(struct io_kiocb *req)
{
struct io_xattr *ix = io_kiocb_to_cmd(req, struct io_xattr);
dismiss_delayed_filename(&ix->filename);
kfree(ix->ctx.kname);
kvfree(ix->ctx.kvalue);
}
static void io_xattr_finish(struct io_kiocb *req, int ret)
{
req->flags &= ~REQ_F_NEED_CLEANUP;
io_xattr_cleanup(req);
io_req_set_res(req, ret, 0);
}
static int __io_getxattr_prep(struct io_kiocb *req,
const struct io_uring_sqe *sqe)
{
struct io_xattr *ix = io_kiocb_to_cmd(req, struct io_xattr);
const char __user *name;
int ret;
INIT_DELAYED_FILENAME(&ix->filename);
ix->ctx.kvalue = NULL;
name = u64_to_user_ptr(READ_ONCE(sqe->addr));
ix->ctx.value = u64_to_user_ptr(READ_ONCE(sqe->addr2));
ix->ctx.size = READ_ONCE(sqe->len);
ix->ctx.flags = READ_ONCE(sqe->xattr_flags);
if (ix->ctx.flags)
return -EINVAL;
ix->ctx.kname = kmalloc_obj(*ix->ctx.kname);
if (!ix->ctx.kname)
return -ENOMEM;
ret = import_xattr_name(ix->ctx.kname, name);
if (ret) {
kfree(ix->ctx.kname);
return ret;
}
req->flags |= REQ_F_NEED_CLEANUP;
req->flags |= REQ_F_FORCE_ASYNC;
return 0;
}
int io_fgetxattr_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
{
return __io_getxattr_prep(req, sqe);
}
int io_getxattr_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
{
struct io_xattr *ix = io_kiocb_to_cmd(req, struct io_xattr);
const char __user *path;
int ret;
if (unlikely(req->flags & REQ_F_FIXED_FILE))
return -EBADF;
ret = __io_getxattr_prep(req, sqe);
if (ret)
return ret;
path = u64_to_user_ptr(READ_ONCE(sqe->addr3));
return delayed_getname(&ix->filename, path);
}
int io_fgetxattr(struct io_kiocb *req, unsigned int issue_flags)
{
struct io_xattr *ix = io_kiocb_to_cmd(req, struct io_xattr);
int ret;
WARN_ON_ONCE(issue_flags & IO_URING_F_NONBLOCK);
ret = file_getxattr(req->file, &ix->ctx);
io_xattr_finish(req, ret);
return IOU_COMPLETE;
}
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/fs.h`, `linux/file.h`, `linux/mm.h`, `linux/slab.h`, `linux/namei.h`, `linux/io_uring.h`.
- Detected declarations: `struct io_xattr`, `function io_xattr_cleanup`, `function io_xattr_finish`, `function __io_getxattr_prep`, `function io_fgetxattr_prep`, `function io_getxattr_prep`, `function io_fgetxattr`, `function io_getxattr`, `function __io_setxattr_prep`, `function io_setxattr_prep`.
- Atlas domain: Kernel Services / io_uring.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.