Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #59781

Bug#885166: instability with 4.14 regarding KVM virtualization

From Jonathan Nieder <jrnieder@gmail.com>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#885166: instability with 4.14 regarding KVM virtualization
Date 2017-12-27 18:40 +0100
Message-ID <v1nQl-4Lw-5@gated-at.bofh.it> (permalink)
References (1 earlier) <v0J6x-1pO-19@gated-at.bofh.it> <v0APD-4bT-1@gated-at.bofh.it> <v1i4i-Qd-5@gated-at.bofh.it> <v0APD-4bT-1@gated-at.bofh.it> <v1i4i-Qd-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Marc Haber wrote:
> On Mon, Dec 25, 2017 at 10:02:48PM +0000, Ben Hutchings wrote:

>> 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.

Yes.  (The main advantage of 'git cherry-pick' over that is that it
performs rename detection, but that shouldn't be relevant here.  You
can similarly do

	git cherry-pick --no-commit fb1522e099f0
	build/test
	git reset --hard
	git bisect good|bad

)

Thanks,
Jonathan

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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