The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Colin King (gmail)" <colin.i.king@gmail.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] dm ioctl: rate limit a couple of ioctl based error messages
Date: Thu, 24 Oct 2024 15:05:34 +0100	[thread overview]
Message-ID: <363880be-dfa3-4cfc-8d7d-613092c36dd0@gmail.com> (raw)
In-Reply-To: <51915860-4a32-b563-c000-d64e1df6702d@redhat.com>

On 24/10/2024 15:01, Mikulas Patocka wrote:
> Hi
> 
> I'd like to ask - have you experienced these errors? What was the process
> that triggered them? Was it some robot that tests syscalls with random
> parameters?

I hit this when running stress-ng's dev test, this exercises various 
ioctls for race conditions.  It's not a major issue, just a corner case 
found when I was running some stress tests.

Colin

> 
> Mikulas
> 
> 
> On Thu, 24 Oct 2024, Colin Ian King wrote:
> 
>> It is possible to spam the kernel log with a misbehaving user process that
>> is passing incorrect dm ioctls to /dev/mapper/control. Use a rate limit
>> on these error messages to reduce the noise.
>>
>> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
>> ---
>>   drivers/md/dm-ioctl.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c
>> index f299ff393a6a..d42eac944eb5 100644
>> --- a/drivers/md/dm-ioctl.c
>> +++ b/drivers/md/dm-ioctl.c
>> @@ -1912,7 +1912,7 @@ static int check_version(unsigned int cmd, struct dm_ioctl __user *user,
>>   
>>   	if ((kernel_params->version[0] != DM_VERSION_MAJOR) ||
>>   	    (kernel_params->version[1] > DM_VERSION_MINOR)) {
>> -		DMERR("ioctl interface mismatch: kernel(%u.%u.%u), user(%u.%u.%u), cmd(%d)",
>> +		DMERR_LIMIT("ioctl interface mismatch: kernel(%u.%u.%u), user(%u.%u.%u), cmd(%d)",
>>   		      DM_VERSION_MAJOR, DM_VERSION_MINOR,
>>   		      DM_VERSION_PATCHLEVEL,
>>   		      kernel_params->version[0],
>> @@ -1961,7 +1961,7 @@ static int copy_params(struct dm_ioctl __user *user, struct dm_ioctl *param_kern
>>   
>>   	if (unlikely(param_kernel->data_size < minimum_data_size) ||
>>   	    unlikely(param_kernel->data_size > DM_MAX_TARGETS * DM_MAX_TARGET_PARAMS)) {
>> -		DMERR("Invalid data size in the ioctl structure: %u",
>> +		DMERR_LIMIT("Invalid data size in the ioctl structure: %u",
>>   		      param_kernel->data_size);
>>   		return -EINVAL;
>>   	}
>> -- 
>> 2.39.5
>>
> 


  reply	other threads:[~2024-10-24 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 11:04 [PATCH][next] dm ioctl: rate limit a couple of ioctl based error messages Colin Ian King
2024-10-24 14:01 ` Mikulas Patocka
2024-10-24 14:05   ` Colin King (gmail) [this message]
2024-10-29 16:44 ` Mike Snitzer
2024-10-31 15:04   ` Mikulas Patocka

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=363880be-dfa3-4cfc-8d7d-613092c36dd0@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@kernel.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