From: Luc Van Oostenryck <lucvoo@kernel.org>
To: "Herbert, Marc" <marc.herbert@intel.com>
Cc: "linux-sparse@vger.kernel.org" <linux-sparse@vger.kernel.org>
Subject: Re: Infinite loop in delete_pseudo_user_list_entry() bisected to commit "cast: optimize away casts to/from pointers"
Date: Thu, 28 Dec 2023 15:21:22 +0100 [thread overview]
Message-ID: <hgs2cgb2auv5y3apocuig6xjhmv3oy5hbzmvjxrxoharjb3fzy@mhjaitwlrnvy> (raw)
In-Reply-To: <4EB87136-D1B0-41CF-B552-9E9F19C00F3B@intel.com>
On Thu, Dec 28, 2023 at 01:08:27AM +0000, Herbert, Marc wrote:
>
> More good news: running `sparse tls.i` on this pre-processed file
> reproduces instantly for me.
Nice!
> So see tls.i file below. In case my mailer mangled the file (I gave up
> on plain text email a long time ago, sorry about that) I also attached
> it to the issue:
> https://github.com/zephyrproject-rtos/zephyr/issues/63417
> I doubt this list accepts attachments...
No problems, I got it alright, thanks.
I think that not too long text attachments (<20M) are OK but I may be wrong.
Anyway, with this it was very easy to reproduce and find the cause.
Fixed and pushed, so mainline Sparse should be OK now.
Many thanks for the bug report,
-- Luc
next prev parent reply other threads:[~2023-12-28 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6A3A9274-C059-467A-89A8-54815D5461BC@intel.com>
2023-12-27 8:00 ` Infinite loop in delete_pseudo_user_list_entry() bisected to commit "cast: optimize away casts to/from pointers" Herbert, Marc
2023-12-27 23:46 ` Luc Van Oostenryck
2023-12-28 1:08 ` Herbert, Marc
2023-12-28 14:21 ` Luc Van Oostenryck [this message]
2024-01-19 23:09 ` Christmas wish list: -Werror and -Wno-warn-about-X Herbert, Marc
2024-01-20 1:27 ` Luc Van Oostenryck
2024-10-09 21:18 ` Herbert, Marc
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=hgs2cgb2auv5y3apocuig6xjhmv3oy5hbzmvjxrxoharjb3fzy@mhjaitwlrnvy \
--to=lucvoo@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=marc.herbert@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).