Bug#885166: instability with 4.14 regarding KVM virtualization

From	Marc Haber <mh+debian-bugs@zugschlus.de>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#885166: instability with 4.14 regarding KVM virtualization
Date	2017-12-27 12:30 +0100
Message-ID	<v1i4i-Qd-5@gated-at.bofh.it> (permalink)
References	<v0APD-4bT-1@gated-at.bofh.it> <v0J6x-1pO-19@gated-at.bofh.it> <v0APD-4bT-1@gated-at.bofh.it> <v0J6x-1pO-19@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

On Mon, Dec 25, 2017 at 10:02:48PM +0000, Ben Hutchings wrote:
> It's on a branch that started at 4.13-rc7 but wasn't merged into
> mainline until after 4.13.  Comparing the two of them, 569dbb88e80d has
> the addition of commit fb1522e099f0 "KVM: update to new mmu_notifier
> semantic v2".  So I would guess that what you landed on is a different
> bug than the one you were looking for.

Ouch. Two bugs with such similiar behavior in a single kernel release?

> Given that commit fb1522e099f0 was merged after -rc7 I assume it's an
> important fix, though the commit message doesn't spell that out.  So I
> think that whenever bisect asks you to test a version that doesn't
> contain it, you should cherry-pick it first to avoid the other bug.  (I
> think you will then need to use 'git bisect good|bad HEAD^' after
> testing, rather than implicitly flagging the current head commit.)

Would
  git show fb1522e099f0 | patch -p1
  build/test
  git reset --hard
  git bisect good|bad
be the same thing? I would feel much more comfortable with that.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Thread

Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2017-12-25 14:20 +0100
  Bug#885166: instability with 4.14 regarding KVM virtualization Ben Hutchings <ben@decadent.org.uk> - 2017-12-25 23:10 +0100
    Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2017-12-27 12:30 +0100
      Bug#885166: instability with 4.14 regarding KVM virtualization Jonathan Nieder <jrnieder@gmail.com> - 2017-12-27 18:40 +0100
      Bug#885166: instability with 4.14 regarding KVM virtualization Ben Hutchings <ben@decadent.org.uk> - 2017-12-27 20:50 +0100
    Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2018-01-08 10:00 +0100
      Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2018-02-11 14:50 +0100
        Bug#885166: instability with 4.14 regarding KVM virtualization Salvatore Bonaccorso <carnil@debian.org> - 2018-02-18 10:20 +0100
          Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2018-02-18 11:40 +0100
            Bug#885166: instability with 4.14 regarding KVM virtualization Salvatore Bonaccorso <carnil@debian.org> - 2018-02-19 06:40 +0100
              Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2018-02-21 16:10 +0100
                Bug#885166: instability with 4.14 regarding KVM virtualization Marc Haber <mh+debian-bugs@zugschlus.de> - 2018-02-23 09:20 +0100

csiph-web