From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: linux-integrity@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
Stuart Yoder <stuart.yoder@arm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Chu Guangqing <chuguangqing@inspur.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tpm_crb: Remove dead code from crb_map_res()
Date: Mon, 12 Oct 2026 16:31:41 +0300 [thread overview]
Message-ID: <aszhPcubTH8HKxh2@kernel.org> (raw)
In-Reply-To: <asy0K_6VkuAn9rTB@sgarzare-redhat>
On Mon, Oct 12, 2026 at 12:23:05PM +0200, Stefano Garzarella wrote:
> On Sun, Oct 11, 2026 at 02:54:57AM +0300, Jarkko Sakkinen wrote:
> > In all the pre-existing call sites both @iomem and @iobase_ptr are either
>
> Do you mean @iores ?
>
> > both NULL or have a valid address.
> >
> > Add an invariant for the expeced conditions and remove a dead basic block.
> > The second block is dead given that if @iomem turns out not to be NULL,
> > neither can't be @iobase_ptr.
> >
> > Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> > ---
> > v2:
> > - Updated the commit message in order to clarify things better.
> > - Updated the invariant in order to address checkpatch.pl --strict
> > errors.
> > drivers/char/tpm/tpm_crb.c | 9 +++------
> > 1 file changed, 3 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c
> > index ceb4100ba400..833226966fa2 100644
> > --- a/drivers/char/tpm/tpm_crb.c
> > +++ b/drivers/char/tpm/tpm_crb.c
> > @@ -570,15 +570,12 @@ static void __iomem *crb_map_res(struct device *dev, struct resource *iores,
> > if (start != new_res.start)
> > return IOMEM_ERR_PTR(-EINVAL);
> >
> > + if (!iores != !iobase_ptr)
> > + return IOMEM_ERR_PTR(-EINVAL);
> > +
> > if (!iores)
> > return devm_ioremap_resource(dev, &new_res);
> >
> > - if (!*iobase_ptr) {
>
> Sorry to insist, but in the commit description we talk about @iobase_ptr
> can't be null, and I agree, but here we were checking the value of the
> pointer, so IMO this code was not dead.
>
> But again, I know nothing on this code. So, if you think it's correct go
> head, I'm surely missing something.
Ugh, you're actually right, and this is not, and should not have sent
this. And it is for lazy init.
I need to sanity check my test environment because I thought I was
testing this with swtpm emulated tpm_crb but tests passed, and this
should not work.
Sorry and thanks :-)
Just wanted to make it explicit that I was making somehting extremely
stupid.
>
> Thanks,
> Stefano
>
> > - *iobase_ptr = devm_ioremap_resource(dev, iores);
> > - if (IS_ERR(*iobase_ptr))
> > - return *iobase_ptr;
> > - }
> > -
> > return *iobase_ptr + (new_res.start - iores->start);
> > }
> >
> > --
> > 2.47.3
> >
>
Br, Jarkko
next prev parent reply other threads:[~2026-10-12 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 23:54 [PATCH v2] tpm_crb: Remove dead code from crb_map_res() Jarkko Sakkinen
2026-10-12 10:23 ` Stefano Garzarella
2026-10-12 13:31 ` Jarkko Sakkinen [this message]
2026-10-12 13:53 ` Jarkko Sakkinen
2026-10-12 14:16 ` Stefano Garzarella
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=aszhPcubTH8HKxh2@kernel.org \
--to=jarkko@kernel.org \
--cc=chuguangqing@inspur.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rafael.j.wysocki@intel.com \
--cc=sgarzare@redhat.com \
--cc=stuart.yoder@arm.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