linux-kernel - Re: [PATCH][next] dm ioctl: rate limit a couple of ioctl based error messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d731f5f9-087d-50b9-998f-d9baac4fdb98@redhat.com>
Date: Thu, 31 Oct 2024 16:04:38 +0100 (CET)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Mike Snitzer <snitzer@...nel.org>
cc: Colin Ian King <colin.i.king@...il.com>, Alasdair Kergon <agk@...hat.com>, 
    dm-devel@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] dm ioctl: rate limit a couple of ioctl based error
 messages



On Tue, 29 Oct 2024, Mike Snitzer wrote:

> On Thu, Oct 24, 2024 at 12:04:31PM +0100, 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@...il.com>
> 
> Mikulas, please update the header to include the context that
> stress-ng is what Colin was using when he experienced excessive
> warnings.
> 
> Thanks.
> 
> Acked-by: Mike Snitzer <snitzer@...nel.org>

OK, done.

Mikulas