linux-kernel - Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new

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]

Message-ID: <75959fca-bb32-53b3-e5ee-ab29dfec34d9@web.de>
Date:   Wed, 3 Jun 2020 08:48:40 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Wang Hai <wanghai38@...wei.com>, linuxppc-dev@...ts.ozlabs.org,
        Andrew Donnellan <ajd@...ux.ibm.com>,
        Arnd Bergmann <arnd@...db.de>,
        Frederic Barrat <fbarrat@...ux.ibm.com>,
        Ian Munsie <imunsie@....ibm.com>, linux-kernel@...r.kernel.org,
        kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()

> Please note that you are responding to someone that a lot of kernel
> developers and maintainers have blacklisted as being very annoying

I can understand that you can occasionally become annoyed.


> and not helpful at all.

I got the impression that some contributors (including you)
found also a selection of my contributions useful.


> Please do not feel that you need to respond to, or change any patch in
> response to their emails at all.

I suggest to reconsider your responses to provided information once more.


> I strongly recommend you just add them to your filters to not have to
> see their messages.  That's what I have done.

I find such an “advice” questionable while it is generally possible
to adjust the communication settings as needed.

Regards,
Markus