[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c93e924f-dc0e-4114-b0a1-3e3ed360a37d@amd.com>
Date: Wed, 8 Nov 2023 12:09:55 -0600
From: Avadhut Naik <avadnaik@....com>
To: "Luck, Tony" <tony.luck@...el.com>,
Avadhut Naik <avadhut.naik@....com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Cc: "rafael@...nel.org" <rafael@...nel.org>,
"lenb@...nel.org" <lenb@...nel.org>,
"james.morse@....com" <james.morse@....com>,
"bp@...en8.de" <bp@...en8.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alexey.kardashevskiy@....com" <alexey.kardashevskiy@....com>,
"yazen.ghannam@....com" <yazen.ghannam@....com>
Subject: [RESEND v5 2/4] fs: debugfs: Add write functionality to debugfs blobs
Hi,
On 11/7/2023 16:28, Luck, Tony wrote:
>> @@ -1042,7 +1060,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);
>> }
>
> The minimalist change here would be to s/0444/0666/
>
> That would just allow callers to ask for writeable files without letting them
> add execute permission, or exotic modes like setuid etc.
>
Noted. Thanks for the clarification. Will change to something like below:
return debugfs_create_file_unsafe(name, mode & 0666, parent, blob, &fops_blob);
> -Tony
--
Thanks,
Avadhut Naik
Powered by blists - more mailing lists