linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@amd.com>
To: Avadhut Naik <Avadhut.Naik@amd.com>,
	rafael@kernel.org, gregkh@linuxfoundation.org, lenb@kernel.org,
	linux-acpi@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: avadnaik@amd.com, yazen.ghannam@amd.com,
	alexey.kardashevskiy@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/3] fs: debugfs: Add write functionality to debugfs blobs
Date: Thu, 8 Jun 2023 14:02:29 +1000	[thread overview]
Message-ID: <a310a133-8d4e-0870-adef-0b7b47a452e7@amd.com> (raw)
In-Reply-To: <20230525204422.4754-3-Avadhut.Naik@amd.com>



On 26/5/23 06:44, Avadhut Naik wrote:
> Currently, debugfs_create_blob() creates read-only debugfs binary blob
> files.
> 
> In some cases, however, userspace tools need to write variable length
> data structures into predetermined memory addresses. An example is when
> injecting Vendor-defined error types through the einj module. In such
> cases, the functionality to write to these blob files in debugfs would
> be desired since the mapping aspect can be handled within the modules
> with userspace tools only needing to write into the blob files.
> 
> Implement a write callback to enable writing to these blob files in
> debugfs.
> 
> Signed-off-by: Avadhut Naik <Avadhut.Naik@amd.com>

Reviewed-by: Alexey Kardashevskiy <aik@amd.com>

> ---
>   fs/debugfs/file.c | 28 +++++++++++++++++++++++-----
>   1 file changed, 23 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> index 1f971c880dde..fab5a562b57c 100644
> --- a/fs/debugfs/file.c
> +++ b/fs/debugfs/file.c
> @@ -973,17 +973,35 @@ static ssize_t read_file_blob(struct file *file, char __user *user_buf,
>   	return r;
>   }
>   
> +static ssize_t write_file_blob(struct file *file, const char __user *user_buf,
> +			       size_t count, loff_t *ppos)
> +{
> +	struct debugfs_blob_wrapper *blob = file->private_data;
> +	struct dentry *dentry = F_DENTRY(file);
> +	ssize_t r;
> +
> +	r = debugfs_file_get(dentry);
> +	if (unlikely(r))
> +		return r;
> +	r = simple_write_to_buffer(blob->data, blob->size, ppos, user_buf,
> +				   count);
> +
> +	debugfs_file_put(dentry);
> +	return r;
> +}
> +
>   static const struct file_operations fops_blob = {
>   	.read =		read_file_blob,
> +	.write =	write_file_blob,
>   	.open =		simple_open,
>   	.llseek =	default_llseek,
>   };
>   
>   /**
> - * debugfs_create_blob - create a debugfs file that is used to read a binary blob
> + * debugfs_create_blob - create a debugfs file that is used to read and write
> + * a binary blob
>    * @name: a pointer to a string containing the name of the file to create.
> - * @mode: the read permission that the file should have (other permissions are
> - *	  masked out)
> + * @mode: the permission that the file should have
>    * @parent: a pointer to the parent dentry for this file.  This should be a
>    *          directory dentry if set.  If this parameter is %NULL, then the
>    *          file will be created in the root of the debugfs filesystem.
> @@ -992,7 +1010,7 @@ static const struct file_operations fops_blob = {
>    *
>    * This function creates a file in debugfs with the given name that exports
>    * @blob->data as a binary blob. If the @mode variable is so set it can be
> - * read from. Writing is not supported.
> + * read from and written to.
>    *
>    * This function will return a pointer to a dentry if it succeeds.  This
>    * pointer must be passed to the debugfs_remove() function when the file is
> @@ -1007,7 +1025,7 @@ struct dentry *debugfs_create_blob(const char *name, umode_t mode,
>   				   struct dentry *parent,
>   				   struct debugfs_blob_wrapper *blob)
>   {
> -	return debugfs_create_file_unsafe(name, mode & 0444, parent, blob, &fops_blob);
> +	return debugfs_create_file_unsafe(name, mode, parent, blob, &fops_blob);
>   }
>   EXPORT_SYMBOL_GPL(debugfs_create_blob);
>   

-- 
Alexey

  reply	other threads:[~2023-06-08  4:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 20:44 [RFC PATCH v2 0/3] Add support for Vendor Defined Error Types in Einj Module Avadhut Naik
2023-05-25 20:44 ` [RFC PATCH v2 1/3] ACPI: APEI: EINJ: Refactor available_error_type_show() Avadhut Naik
2023-06-07 14:20   ` Yazen Ghannam
2023-06-08  3:48     ` Alexey Kardashevskiy
2023-06-08 21:08       ` Avadhut Naik
2023-05-25 20:44 ` [RFC PATCH v2 2/3] fs: debugfs: Add write functionality to debugfs blobs Avadhut Naik
2023-06-08  4:02   ` Alexey Kardashevskiy [this message]
2023-05-25 20:44 ` [RFC PATCH v2 3/3] ACPI: APEI: EINJ: Add support for vendor defined error types Avadhut Naik
2023-06-08  4:44   ` Alexey Kardashevskiy
2023-06-08 21:18     ` Avadhut Naik

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=a310a133-8d4e-0870-adef-0b7b47a452e7@amd.com \
    --to=aik@amd.com \
    --cc=Avadhut.Naik@amd.com \
    --cc=alexey.kardashevskiy@amd.com \
    --cc=avadnaik@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=yazen.ghannam@amd.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;
as well as URLs for NNTP newsgroup(s).