linux-kernel - Re: [PATCH] EDAC/sysfs: Fix calling kobject

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: <abfe20ea-80e9-4688-a689-110399a900da@oracle.com>
Date:   Wed, 29 Nov 2023 00:06:16 +0530
From:   Harshit Mogalapalli <harshit.m.mogalapalli@...cle.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Borislav Petkov <bp@...en8.de>, Tony Luck <tony.luck@...el.com>,
        James Morse <james.morse@....com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Robert Richter <rric@...nel.org>, linux-edac@...r.kernel.org,
        linux-kernel@...r.kernel.org, dan.carpenter@...aro.org,
        kernel-janitors@...r.kernel.org, error27@...il.com
Subject: Re: [PATCH] EDAC/sysfs: Fix calling kobject_put() without kobj
 initialization

Hi Greg,

On 28/11/23 11:25 pm, Harshit Mogalapalli wrote:
> Hi Greg,
> 
> 
>> This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
>> a patch that has triggered this response.  He used to manually respond
>> to these common problems, but in order to save his sanity (he kept
>> writing the same thing over and over, yet to different people), I was
>> created.  Hopefully you will not take offence and will fix the problem
>> in your patch and resubmit it so that it can be accepted into the Linux
>> kernel tree.
>>
>> You are receiving this message because of the following common error(s)
>> as indicated below:
>>
>> - This looks like a new version of a previously submitted patch, but you
>>    did not list below the --- line any changes from the previous version.
>>    Please read the section entitled "The canonical patch format" in the
>>    kernel file, Documentation/process/submitting-patches.rst for what
>>    needs to be done here to properly describe this.
>>
>> - You have marked a patch with a "Fixes:" tag for a commit that is in an
>>    older released kernel, yet you do not have a cc: stable line in the
>>    signed-off-by area at all, which means that the patch will not be
>>    applied to any older kernel releases.  To properly fix this, please
>>    follow the documented rules in the
>>    Documentation/process/stable-kernel-rules.rst file for how to resolve
>>    this.
>>
>> If you wish to discuss this problem further, or you have questions about
>> how to resolve this issue, please feel free to respond to this email and
>> Greg will reply once he has dug out from the pending patches received
>> from other developers.
> 
> No, this is a similar bug but in the edac_pci_sysfs.c file instead of 
> the edac_device_sysfs.c.
> 
> Let me resend these two patches as a patchset and change the subject to 
> make it more obvious(EDAC/pci_sysfs, EDAC/device_sysfs in title).  And 
> add a CC stable tag.
> 

Sent a V2 here as a patch series:
https://lore.kernel.org/all/20231128183037.3395755-1-harshit.m.mogalapalli@oracle.com/

Thanks,
Harshit
> Thanks,
> Harshit
> 
>>
>> thanks,
>>
>> greg k-h's patch email bot
>