From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Pengfei Xu <pengfei.xu@intel.com>, jarkko@kernel.org
Cc: linux-kernel@vger.kernel.org, jgg@ziepe.ca, heng.su@intel.com,
peterhuewe@gmx.de, dhowells@redhat.com, lkp@intel.com
Subject: Re: [Syzkaller & bisect] There is WARNING in tpm_chip_unregister in upstream patch "tpm: st33zp24: Mark ACPI and OF related data as maybe unused"
Date: Wed, 26 Apr 2023 15:12:41 +0200 [thread overview]
Message-ID: <1b67d480-d6f1-965f-ccfa-0874eb9a3b6b@linaro.org> (raw)
In-Reply-To: <ZEjqhwHWBnxcaRV5@xpf.sh.intel.com>
On 26/04/2023 11:10, Pengfei Xu wrote:
> Hi Jarkko and Krzysztof Kozlowski,
>
> Greeting!
>
> Platform: x86 platforms
>
> There is WARNING in tpm_chip_unregister in upstream patch "tpm: st33zp24: Mark
> ACPI and OF related data as maybe unused":
> https://lore.kernel.org/lkml/20230424144130.1084795-1-jarkko@kernel.org/
> -> https://lore.kernel.org/lkml/20230319141354.22907-1-krzysztof.kozlowski@linaro.org/
>
> We tested Intel internal kernel and found that, the above patch caused below
> WARNING and then kernel BUG dmesg info. After reverted above commit on top
> of Intel internal kernel, this issue was gone.
> I checked that internal commit:"c3985d8b9c22 tpm: st33zp24: Mark ACPI and OF
> related data as maybe unused" was same as above link patch.
> This issue could be reproduced in 155s in VM.
>
> All detailed info: https://github.com/xupengfe/syzkaller_logs/tree/main/230426_132902_tpm_chip_unregister_warning
> Syzkaller reproduced code: https://github.com/xupengfe/syzkaller_logs/blob/main/230426_132902_tpm_chip_unregister_warning/repro.c
> Syzkaller syscall reproduced steps: https://github.com/xupengfe/syzkaller_logs/blob/main/230426_132902_tpm_chip_unregister_warning/repro.prog
> Syzkaller analysis report: https://github.com/xupengfe/syzkaller_logs/blob/main/230426_132902_tpm_chip_unregister_warning/repro.report
> Kconfig: https://github.com/xupengfe/syzkaller_logs/blob/main/230426_132902_tpm_chip_unregister_warning/kconfig_origin
> Bisect info: https://github.com/xupengfe/syzkaller_logs/blob/main/230426_132902_tpm_chip_unregister_warning/bisect_info.log
>
> "
> [ 24.638052] memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=329 'systemd'
> [ 28.731375] cgroup: Unknown subsys name 'net'
> [ 28.741433] cgroup: Unknown subsys name 'rlimit'
> [ 35.900833] tpm tpm0: Operation Canceled
> [ 35.901377] ------------[ cut here ]------------
> [ 35.901648] refcount_t: addition on 0; use-after-free.
> [ 35.901986] WARNING: CPU: 0 PID: 4095 at lib/refcount.c:25 refcount_warn_saturate+0xe6/0x1c0
Thanks for the report. I am quite surprised that this commit was pointed
as possible cause. The patch does not touch anything related to reported
issue... At least I do not see it. Could be some tooling problem in your
reproduction steps?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-26 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 9:10 Pengfei Xu
2023-04-26 13:12 ` Krzysztof Kozlowski [this message]
2023-04-26 18:03 ` Jarkko Sakkinen
2023-04-27 2:23 ` Pengfei Xu
2023-04-26 14:26 ` Krzysztof Kozlowski
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=1b67d480-d6f1-965f-ccfa-0874eb9a3b6b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=dhowells@redhat.com \
--cc=heng.su@intel.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pengfei.xu@intel.com \
--cc=peterhuewe@gmx.de \
/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®