linux-kernel - RE: [PATCH] mei: remove dev_err message on an unsupported ioctl

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 27 Feb 2018 21:47:51 +0000
From:   "Winkler, Tomas" <tomas.winkler@...el.com>
To:     Colin Ian King <colin.king@...onical.com>,
        Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] mei: remove dev_err message on an unsupported ioctl


> On 27/02/18 17:26, Winkler, Tomas wrote:
> >>
> >> From: Colin Ian King <colin.king@...onical.com>
> >>
> >> Currently the driver spams the kernel log on unsupported ioctls which
> >> is unnecessary as the ioctl returns -ENOIOCTLCMD to indicate this
> anyway.
> >> I suspect this was originally for debugging purposes but it really is
> >> not required so remove it.
> >>
> >
> > This is rather strange as most of the legimit applications are using
> > one IOCTL from kernel 3.0 Do you have any reference where this call is
> originated from, frankly this is the first time I got such complain.
> 
> I hit this while stressing the kernel with my stress-ng kernel stressing tool;
> this was not using the legitimate ioctls (to see if things
> explode) and I got a rather full kernel log. So it was being abused somewhat
> ;-)

Okay, thanks for the info.