mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@mandelbit.com>
To: Zhihao Cheng <chengzhihao1@huawei.com>, linux-mtd@lists.infradead.org
Cc: Richard Weinberger <richard@nod.at>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ubifs: fix uninitialized variable usage
Date: Mon, 18 Nov 2024 11:02:27 +0100	[thread overview]
Message-ID: <307a2ff6-eeb7-4b86-a5c6-c438dcec618e@mandelbit.com> (raw)
In-Reply-To: <e26aea85-988c-17a1-7fff-c14387ca4b57@huawei.com>

On 16/11/2024 03:02, Zhihao Cheng wrote:
> 在 2024/11/16 6:26, Antonio Quartulli 写道:
>> In ubifs_jnl_write_inode(), when an inode cannot be deleted
>> due to too many xattrs, err is passed to ubifs_ro_mode()
>> uninitialized, thus leading to bogus error reporting.
>>
>> Fix this case by passing -EPERM, which is the same value that
>> ubifs_jnl_write_inode() is going to return to the caller.
>>
>> This fixes 1 UNINIT issue reported by Coverity
>> Report: CID 1601860: Uninitialized scalar variable (UNINIT)
>>
>> Cc: Richard Weinberger <richard@nod.at>
>> Cc: Zhihao Cheng <chengzhihao1@huawei.com>
>> Cc: linux-kernel@vger.kernel.org (open list)
>> Signed-off-by: Antonio Quartulli <antonio@mandelbit.com>
>> ---
>>   fs/ubifs/journal.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Hi Antonio, thanks for the patch. Nathan has sent a patch to fix it.
> https://lore.kernel.org/linux-mtd/ 
> b560f413-70f1-8ebb-7403-34591658ca86@huawei.com/T/#t

Perfect!
Thanks for letting me know.

Regards,


-- 
Antonio Quartulli

CEO and Co-Founder
Mandelbit Srl
https://www.mandelbit.com


      reply	other threads:[~2024-11-18 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 22:26 Antonio Quartulli
2024-11-16  2:02 ` Zhihao Cheng
2024-11-18 10:02   ` Antonio Quartulli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=307a2ff6-eeb7-4b86-a5c6-c438dcec618e@mandelbit.com \
    --to=antonio@mandelbit.com \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®