From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Roman Demidov <roman.demidov@red-soft.ru>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] ocfs2: Remove redundant NULL check for rec variable
Date: Thu, 30 Jul 2026 18:41:03 -0700 [thread overview]
Message-ID: <20260730184103.95a1e280e006e6bbc149ba30@linux-foundation.org> (raw)
In-Reply-To: <a62a1071-4134-4bd6-b4fe-5b4f278037a9@linux.alibaba.com>
On Fri, 31 Jul 2026 08:44:58 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:
>
>
> On 7/30/26 9:15 PM, Roman Demidov wrote:
> > The rec variable will contain the address of the structure array element,
> > i.e., the address of the ocfs2_chain_rec structure.
> > This address cannot be NULL.
> >
> > Found by Linux Verification Center (linuxtesting.org) with SVACE.
> >
> > Signed-off-by: Roman Demidov <roman.demidov@red-soft.ru>
>
> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
Thanks. And thanks Roman.
But I'm afraid we aren't supposed to take patches from developers with
Russian affiliations. Especially those which are on the OFAC list,
which appears to be the case with red-soft.ru.
https://share.google/aimode/UgHJ7ubsy9uflS1Qa
https://share.google/aimode/wpqMe0GiORkYi2meC
prev parent reply other threads:[~2026-07-31 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:15 [PATCH] ocfs2: Remove redundant NULL check for rec variable Roman Demidov
2026-07-31 0:44 ` Joseph Qi
2026-07-31 1:41 ` Andrew Morton [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=20260730184103.95a1e280e006e6bbc149ba30@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=roman.demidov@red-soft.ru \
/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