From: Christoph Hellwig <hch@infradead.org>
To: Jeremy Bingham <jbingham@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
brauner@kernel.org, jkoolstra@xs4all.nl, jack@suse.cz,
djwong@kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 1/5] iomap: add iomap_symlink_write
Date: Mon, 13 Jul 2026 02:44:13 -0700 [thread overview]
Message-ID: <alSzbXMbr-fy9hwQ@infradead.org> (raw)
In-Reply-To: <570b47ec69233efcdde6644fc11bc5a8af6a9577.1783707063.git.jbingham@gmail.com>
On Sat, Jul 11, 2026 at 01:59:05PM -0700, Jeremy Bingham wrote:
> Add a new iomap_symlink_write function as an iomap based equivalent to
> page_symlink found in fs/namei.c. This implementation was suggested by
> Darrick J. Wong, who also provided the initial implementation that I
> only needed to change slightly to get working.
>
> Suggested-by: Darrick J. Wong <djwong@kernel.org>
>
> Signed-off-by: Jeremy Bingham <jbingham@gmail.com>
No empty line between tags pleaase.
> +int iomap_symlink_write(struct inode *inode, const char *target, int len,
> + const struct iomap_ops *ops,
> + const struct iomap_write_ops *write_ops, void *private)
There is nothign symlink-specific in this code. It's really just a
low-level write that doesn't need an iocb.
> + while ((ret = iomap_iter(&iter, ops)) > 0)
> + iter.status = iomap_write_iter(&iter, &iov, write_ops);
> +
> + if (unlikely(iter.pos == 0))
> + return ret;
> +
> + mark_inode_dirty(inode);
And given that a normal write doesn't mark the inode dirty we should
probably leave this to the caller for consistency.
> + return 0;
And maybe also return the length writtenn for consistency? Or if we
avoid partial writes for some reason, return an error when they happen?
next prev parent reply other threads:[~2026-07-13 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 20:59 [PATCH v3 0/5] minix: convert to iomap and add direct I/O Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 1/5] iomap: add iomap_symlink_write Jeremy Bingham
2026-07-13 9:44 ` Christoph Hellwig [this message]
2026-07-11 20:59 ` [PATCH v3 2/5] minix: add base iomap begin/end functions Jeremy Bingham
2026-07-13 9:46 ` Christoph Hellwig
2026-07-11 20:59 ` [PATCH v3 3/5] minix: update itree* files to add iomap functions Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 4/5] minix: add file operation functions Jeremy Bingham
2026-07-13 9:48 ` Christoph Hellwig
2026-07-13 19:17 ` Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 5/5] minix: iomap inode operations Jeremy Bingham
2026-07-13 9:32 ` [PATCH v3 0/5] minix: convert to iomap and add direct I/O Christoph Hellwig
2026-07-13 19:26 ` Jeremy Bingham
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=alSzbXMbr-fy9hwQ@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=jbingham@gmail.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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