From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>,
"Ethan Tidmore" <ethantidmore06@gmail.com>,
"Carlos Maiolino" <cem@kernel.org>, "NeilBrown" <neil@brown.name>
Cc: "Christian Brauner" <brauner@kernel.org>,
<linux-xfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: Fix error pointer dereference
Date: Thu, 19 Feb 2026 10:46:51 -0600 [thread overview]
Message-ID: <DGJ3AIJ080KO.3MUES6EQ1TWDA@gmail.com> (raw)
In-Reply-To: <61386abf00c817e65ab70c994ed584fde339f9ed.camel@gmail.com>
On Thu Feb 19, 2026 at 5:26 AM CST, Nirjhar Roy (IBM) wrote:
> On Wed, 2026-02-18 at 13:51 -0600, Ethan Tidmore wrote:
...
>
> Based on my limited knowledge of this change looks okay to me. I looked into the return values of
> try_lookup_noperm() and it does return error pointer which is not NULL. I also checked the other
> call sites of try_lookup_noperm() but I do see a mixed handling i.e, some places just checks for
> !ptr and some for IS_ERR_OR_NULL. For example in fs/autofs it checks with IS_ERR_OR_NULL whereas in
> fs/proc/base.c it just checks for !child. However, IMO, it is better to check for both NULL and
> error pointer if there is a possibility for both.
> --NR
I was already planning on sending a patch to fs/proc/base.c also. Smatch
was complaining there too.
Thanks,
ET
prev parent reply other threads:[~2026-02-19 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 19:51 [PATCH] xfs: Fix error pointer dereference Ethan Tidmore
2026-02-18 23:49 ` Darrick J. Wong
2026-02-19 0:25 ` NeilBrown
2026-02-19 0:31 ` Darrick J. Wong
2026-02-19 0:21 ` NeilBrown
2026-02-19 11:26 ` Nirjhar Roy (IBM)
2026-02-19 16:46 ` Ethan Tidmore [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=DGJ3AIJ080KO.3MUES6EQ1TWDA@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=nirjhar.roy.lists@gmail.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