tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bugspray Bot <bugbot@kernel.org>
To: andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	tools@kernel.org,  konstantin@linuxfoundation.org,
	marmarek@invisiblethingslab.com
Subject: Re: b4 inserts Reviewed-by tag from unrelated thread/patch
Date: Mon, 28 Apr 2025 21:30:26 +0000 (UTC)	[thread overview]
Message-ID: <20250428-b219993c2-49c69b8f53c5@bugzilla.kernel.org> (raw)
In-Reply-To: <b19f33bc-df96-4365-bef4-7f1393fc7ce3@citrix.com>

Konstantin Ryabitsev writes in commit 048adc880245925f7a62639fc0cc58c9e086b3f1:

Fix trailer attribution bug due to incorrect thread traversing

When we were walking the thread looking for where the trailer belongs,
we were incorrectly attributing trailers sent to a single patch as if it
were sent to the cover letter. This only happened in the following
situation

 [PATCH 0/X] Cover Letter
 |
 |---> [PATCH Y/X] Patch Y
 |     (patch being reviewed)
 |
 |-----> Re: [PATCH Y/X] Patch Y
 |       (follow-up that *doesn't* contain a trailer)
 |
 |-------> Re: [PATCH Y/X] Patch Y
 |         (follow-up that *does* contains a trailer)

In this case we had a bug in traversing the references where we first
looked at the immediate parent, and then straight at the top of the
thread, becaues the references were not reversed when we had parsed
them.

This patch fixes both the incorrect order of references AND it doesn't
trust them to be in the correct order -- it will now always rely on the
in-reply-to header to figure out what the parent of the message is.

Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=219993
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>

(via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=048adc880245)
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


      parent reply	other threads:[~2025-04-28 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 13:18 b4 inserts Reviewed-by tag from unrelated thread/patch Andrew Cooper
2025-04-08 14:51 ` Konstantin Ryabitsev
2025-04-08 14:55 ` Bugspray Bot
2025-04-28 21:30 ` Bugspray Bot [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=20250428-b219993c2-49c69b8f53c5@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=konstantin@linuxfoundation.org \
    --cc=marmarek@invisiblethingslab.com \
    --cc=tools@kernel.org \
    /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 NNTP newsgroup(s).