[Bug 216388] On Host, kernel errors in KVM, on guests, it shows CPU stalls

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=216388

--- Comment #19 from Sean Christopherson (seanjc@google.com) ---
On Sat, Sep 03, 2022, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216388
> 
> --- Comment #15 from Robert Dinse (nanook@eskimo.com) ---
> Please forgive my lack of knowledge regarding git, but is there a way to get
> a
> patch that took the kernel from 5.18.19 to 5.19.0 now that earlier releases
> of
> 5.19.x are not on the kernel.org site?

Strictly speaking, no.  Stable branches, i.e. v5.18.x in this case, are
effectively
forks.  After v5.18.0, everything that goes into v5.18.y is a unique commit,
even
if bug fixes are based on an upstream (master branch) commit.

Visually, it's something like this.

v5.18.0 --> v5.18.1 --> v5.18.2 --> v5.18.y
\
 -> ... -> v5.19.0 -> v5.19.1
           \
            -> ... -> v5.20


IIUC, in this situation v5.18.0 isn't stable enough to test on its own, but the
v5.18.19 candidate is fully healthy.  In that case, if you wanted to bisect
between
v5.18.0 and v5.19.0 to figure out what broke in v5.19, the least awful approach
would be to first find what commit(s) between v5.18.0 and v5.18.19 fixed the
unrelated
instability in v5.18.0, and then manually apply that commit(s) at every stage
when
bisecting between v5.18.0 and v5.19.0 to identify the buggy commit that
introduced
the CPU/RCU stalls.

> I know there is a patch that goes from 5.18.19 to 5.19.6

I assume you mean v5.18.19 => v5.18.20?

> and one that goes 5.19.5 to 5.19.6 but I just want to look at the changes
> between 5.18.19 and 5.19.0.

If you just want to look at the changes, you can always do

        git diff <commit A>..<commit B>

e.g.

        git diff v5.18.18..v5.19

but that's going to show _all_ changes in a single diff, i.e. pinpointing
exactly
what change broke/fixed something is extremely difficult.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.