From: Markus Elfring <Markus.Elfring@web.de>
To: Philipp Hahn <phahn-oss@avm.de>, linux-fsdevel@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
Yuezhang Mo <yuezhang.mo@sony.com>
Subject: Re: exfat: Fix 2 issues found by static code analysis
Date: Thu, 5 Mar 2026 11:51:37 +0100 [thread overview]
Message-ID: <3125ae55-e592-4491-9599-4fceb483d882@web.de> (raw)
In-Reply-To: <aahL4icRtdiZIhwC@mail-auth.avm.de>
>>> I'm going through our list of issues found by static code analysis using Klocwork.
>>
>> Does this tool point any more implementation details out for further development considerations
>> (with other software components)?
>
> This was a run on our internal version of exfat, which matches
> 'github.com/namjaejeon/linux-exfat-oot/for-kernel-version-from-4.1.0'.
Thanks for such background information.
> If my time permits I will run it again on latest 'linux-7.0-rc`
> respective 'master' to see if anything "new" crept in.
It is probably nicer to repeat source code analyses on more recent
software revisions occasionally.
> I'll also report any other findings outside of exfat when I find them.
I became curious on the aspect on how many development resources
you may invest then.
Regards,
Markus
next prev parent reply other threads:[~2026-03-05 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 10:59 [PATCH] exfat: Fix 2 issues found by static code analysis Philipp Hahn
2026-03-03 10:59 ` [PATCH] exfat: Fix bitwise operation having different size Philipp Hahn
2026-03-03 10:59 ` [PATCH] exfat: Drop dead assignment of num_clusters Philipp Hahn
2026-03-03 11:50 ` Markus Elfring
2026-03-04 8:07 ` Philipp Hahn
2026-03-04 8:40 ` exfat: Fix 2 issues found by static code analysis Markus Elfring
2026-03-04 15:12 ` Philipp Hahn
2026-03-05 10:51 ` Markus Elfring [this message]
2026-03-04 10:25 ` [PATCH] " Namjae Jeon
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=3125ae55-e592-4491-9599-4fceb483d882@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phahn-oss@avm.de \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.com \
/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