From: Randy Dunlap <rdunlap@infradead.org>
To: Max Kellermann <max.kellermann@ionos.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] pipe_fs_i.h: add pipe_buf_init()
Date: Tue, 19 Sep 2023 14:40:55 -0700 [thread overview]
Message-ID: <f185463b-4781-4e63-894b-c3592e3c0852@infradead.org> (raw)
In-Reply-To: <20230919080707.1077426-1-max.kellermann@ionos.com>
Hi--
On 9/19/23 01:07, Max Kellermann wrote:
> Adds one central function which shall be used to initialize a newly
> allocated struct pipe_buffer. This shall make the pipe code more
> robust for the next time the pipe_buffer struct gets modified, to
> avoid leaving new members uninitialized. Instead, adding new members
> should also add a new pipe_buf_init() parameter, which causes
> compile-time errors in call sites that were not adapted.
>
> This commit doesn't refactor fs/fuse/dev.c because this code looks
> obscure to me; it initializes pipe_buffers incrementally through a
> variety of functions, too complicated for me to understand.
>
> Signed-off-by: Max Kellermann <max.kellermann@ionos.com>
> ---
> fs/pipe.c | 9 +++------
> fs/splice.c | 9 ++++-----
> include/linux/pipe_fs_i.h | 20 ++++++++++++++++++++
> kernel/watch_queue.c | 8 +++-----
> mm/filemap.c | 8 ++------
> mm/shmem.c | 9 +++------
> 6 files changed, 35 insertions(+), 28 deletions(-)
>
> diff --git a/include/linux/pipe_fs_i.h b/include/linux/pipe_fs_i.h
> index 608a9eb86bff..2ef2bb218641 100644
> --- a/include/linux/pipe_fs_i.h
> +++ b/include/linux/pipe_fs_i.h
> @@ -176,6 +176,26 @@ static inline struct pipe_buffer *pipe_head_buf(const struct pipe_inode_info *pi
> return pipe_buf(pipe, pipe->head);
> }
>
> +/**
> + * Initialize a struct pipe_buffer.
> + */
That's not a kernel-doc comment so don't begin it with /**.
Just use /* instead.
Thanks.
> +static inline void pipe_buf_init(struct pipe_buffer *buf,
> + struct page *page,
> + unsigned int offset, unsigned int len,
> + const struct pipe_buf_operations *ops,
> + unsigned int flags)
> +{
> + buf->page = page;
> + buf->offset = offset;
> + buf->len = len;
> + buf->ops = ops;
> + buf->flags = flags;
> +
> + /* not initializing the "private" member because it is only
> + used by pipe_buf_operations which inject it via struct
> + partial_page / struct splice_pipe_desc */
> +}
> +
> /**
> * pipe_buf_get - get a reference to a pipe_buffer
> * @pipe: the pipe that the buffer belongs to
--
~Randy
prev parent reply other threads:[~2023-09-19 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:07 Max Kellermann
2023-09-19 13:45 ` Christian Brauner
2023-09-19 13:55 ` Max Kellermann
2023-09-19 14:16 ` Christian Brauner
2023-09-19 22:39 ` Max Kellermann
2023-09-19 21:40 ` Randy Dunlap [this message]
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=f185463b-4781-4e63-894b-c3592e3c0852@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=max.kellermann@ionos.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox