netdev - Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device

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:   Sat, 8 Feb 2020 07:59:17 +0100
From:   Christian Zigotzky <chzigotzky@...osoft.de>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Michael Ellerman <mpe@...erman.id.au>,
        Jakub Kicinski <kuba@...nel.org>,
        Christophe Leroy <christophe.leroy@....fr>,
        DTML <devicetree@...r.kernel.org>,
        Darren Stevens <darren@...vens-zone.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linuxppc-dev@...abs.org, "contact@...on.com" <contact@...on.com>,
        "R.T.Dickinson" <rtd2@...a.co.nz>, Christoph Hellwig <hch@....de>,
        mad skateman <madskateman@...il.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Christian Zigotzky <info@...osoft.de>
Subject: Re: Latest Git kernel: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device



> On 7. Feb 2020, at 18:08, Arnd Bergmann <arnd@...db.de> wrote:
> 
> On Fri, Feb 7, 2020 at 3:34 PM Christian Zigotzky
> <chzigotzky@...osoft.de> wrote:
>> 
>> Hello Arnd,
>> 
>> We regularly compile and test Linux kernels every day during the merge
>> window. Since Thursday last week we have very high CPU usage because of
>> the avahi daemon on our desktop Linux systems (Ubuntu, Debian etc). The
>> avahi daemon produces a lot of the following log message. This generates
>> high CPU usage.
>> 
>> Error message: avahi-daemon[2410]: ioctl(): Inappropriate ioctl for device
>> 
>> strace /usr/sbin/avahi-daemon:
>> 
> 
> Thanks a lot for the detailed analysis, with this I immediately saw
> what went wrong in my
> original commit and I sent you a fix. Please test to ensure that this
> correctly addresses
> the problem.
> 
>        Arnd

Hi Arnd,

Thanks a lot for your patch! I will test it as soon as possible.

Cheers,
Christian