Received-SPF: pass (google.com: domain of linux-kernel+bounces-31866-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Message-ID: <3585159b-12f1-43ec-bd85-0253a0534c0e@gmail.com>
Date: Sat, 20 Jan 2024 23:49:15 +0530
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v2] iouring:added boundary value check for io_uring_group
 systl
Content-Language: en-US
To: Jens Axboe <axboe@kernel.dk>, corbet@lwn.net, jmoyer@redhat.com,
 asml.silence@gmail.com, akpm@linux-foundation.org, bhe@redhat.com,
 ribalda@chromium.org, rostedt@goodmis.org, sshegde@linux.vnet.ibm.com,
 alexghiti@rivosinc.com, matteorizzo@google.com, ardb@kernel.org,
 linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
 io-uring@vger.kernel.org
References: <20240120144411.2564-1-subramanya.swamy.linux@gmail.com>
 <f48e47b5-0572-4f84-b165-5a9e91788c57@kernel.dk>
From: Subramanya Swamy <subramanya.swamy.linux@gmail.com>
In-Reply-To: <f48e47b5-0572-4f84-b165-5a9e91788c57@kernel.dk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Jens,

On 20/01/24 22:31, Jens Axboe wrote:
> On 1/20/24 7:44 AM, Subramanya Swamy wrote:
>> /proc/sys/kernel/io_uring_group takes gid as input
>> added boundary value check to accept gid in range of
>> 0<=gid<=4294967294 & Documentation is updated for same
> This should have:
>
> Fixes: 76d3ccecfa18 ("io_uring: add a sysctl to disable io_uring system-wide")
  added fixes to commit msg in v3
>> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
>> index 6584a1f9bfe3..a8b61ab3e118 100644
>> --- a/Documentation/admin-guide/sysctl/kernel.rst
>> +++ b/Documentation/admin-guide/sysctl/kernel.rst
>> @@ -470,10 +470,8 @@ io_uring_group
>>   ==============
>>   
>>   When io_uring_disabled is set to 1, a process must either be
>> -privileged (CAP_SYS_ADMIN) or be in the io_uring_group group in order
>> -to create an io_uring instance.  If io_uring_group is set to -1 (the
>> -default), only processes with the CAP_SYS_ADMIN capability may create
>> -io_uring instances.
>> +privledged (CAP_SYS_ADMIN) or be in the io_uring_group group in order
> privileged.
fixed  typo in v3

-- 
Best Regards
Subramanya