€•Àw      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ*/translations/zh_CN/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/zh_TW/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/it_IT/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/ja_JP/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/ko_KR/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ*/translations/sp_SP/admin-guide/bug-bisect”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ0SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)”h]”hŒ0SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒD/var/lib/git/docbuild/linux/Documentation/admin-guide/bug-bisect.rst”h Kubh¢)”}”(hŒ<[see the bottom of this file for redistribution information]”h]”hŒ<[see the bottom of this file for redistribution information]”…””}”hh´sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hhhžhhŸh³h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒBisecting a regression”h]”hŒBisecting a regression”…””}”(hhÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhhÄhžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒÅThis document describes how to use a ``git bisect`` to find the source code
change that broke something -- for example when some functionality stopped
working after upgrading from Linux 6.0 to 6.1.”h]”(hŒ%This document describes how to use a ”…””}”(hhÙhžhhŸNh NubhŒliteral”“”)”}”(hŒ``git bisect``”h]”hŒ
git bisect”…””}”(hhãhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1háhhÙubhŒ’ to find the source code
change that broke something -- for example when some functionality stopped
working after upgrading from Linux 6.0 to 6.1.”…””}”(hhÙhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hXt  The text focuses on the gist of the process. If you are new to bisecting the
kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
instead: it depicts everything from start to finish while covering multiple
aspects even kernel developers occasionally forget. This includes detecting
situations early where a bisection would be a waste of time, as nobody would
care about the result -- for example, because the problem happens after the
kernel marked itself as 'tainted', occurs in an abandoned version, was already
fixed, or is caused by a .config change you or your Linux distributor performed.”h]”hXx  The text focuses on the gist of the process. If you are new to bisecting the
kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
instead: it depicts everything from start to finish while covering multiple
aspects even kernel developers occasionally forget. This includes detecting
situations early where a bisection would be a waste of time, as nobody would
care about the result -- for example, because the problem happens after the
kernel marked itself as â€˜taintedâ€™, occurs in an abandoned version, was already
fixed, or is caused by a .config change you or your Linux distributor performed.”…””}”(hhûhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhÃ)”}”(hhh]”(hÈ)”}”(hŒ;Finding the change causing a kernel issue using a bisection”h]”hŒ;Finding the change causing a kernel issue using a bisection”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj	  hžhhŸh³h KubhØ)”}”(hX×  *Note: the following process assumes you prepared everything for a bisection.
This includes having a Git clone with the appropriate sources, installing the
software required to build and install kernels, as well as a .config file stored
in a safe place (the following example assumes '~/prepared_kernel_.config') to
use as pristine base at each bisection step; ideally, you have also worked out
a fully reliable and straight-forward way to reproduce the regression, too.*”h]”hŒemphasis”“”)”}”(hj  h]”hXÙ  Note: the following process assumes you prepared everything for a bisection.
This includes having a Git clone with the appropriate sources, installing the
software required to build and install kernels, as well as a .config file stored
in a safe place (the following example assumes â€˜~/prepared_kernel_.configâ€™) to
use as pristine base at each bisection step; ideally, you have also worked out
a fully reliable and straight-forward way to reproduce the regression, too.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj	  hžhubhŒbullet_list”“”)”}”(hhh]”hŒ	list_item”“”)”}”(hX)  Preparation: start the bisection and tell Git about the points in the history
you consider to be working and broken, which Git calls 'good' and 'bad'::

   git bisect start
   git bisect good v6.0
   git bisect bad v6.1

Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
”h]”(hØ)”}”(hŒ—Preparation: start the bisection and tell Git about the points in the history
you consider to be working and broken, which Git calls 'good' and 'bad'::”h]”hŒžPreparation: start the bisection and tell Git about the points in the history
you consider to be working and broken, which Git calls â€˜goodâ€™ and â€˜badâ€™:”…””}”(hj>  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj:  ubhŒliteral_block”“”)”}”(hŒ9git bisect start
git bisect good v6.0
git bisect bad v6.1”h]”hŒ9git bisect start
git bisect good v6.0
git bisect bad v6.1”…””}”hjN  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h K"hj:  ubhØ)”}”(hŒKInstead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.”h]”hŒSInstead of Git tags like â€˜v6.0â€™ and â€˜v6.1â€™ you can specify commit-ids, too.”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K&hj:  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j8  hj5  hžhhŸh³h Nubah}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j3  hŸh³h Khj	  hžhubhŒenumerated_list”“”)”}”(hhh]”(j9  )”}”(hŒ¹Copy your prepared .config into the build directory and adjust it to the
needs of the codebase Git checked out for testing::

  cp ~/prepared_kernel_.config .config
  make olddefconfig
”h]”(hØ)”}”(hŒ|Copy your prepared .config into the build directory and adjust it to the
needs of the codebase Git checked out for testing::”h]”hŒ{Copy your prepared .config into the build directory and adjust it to the
needs of the codebase Git checked out for testing:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K(hj}  ubjM  )”}”(hŒ6cp ~/prepared_kernel_.config .config
make olddefconfig”h]”hŒ6cp ~/prepared_kernel_.config .config
make olddefconfig”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h K+hj}  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j8  hjz  hžhhŸh³h Nubj9  )”}”(hŒôNow build, install, and boot a kernel. This might fail for unrelated reasons,
for example, when a compile error happens at the current stage of the
bisection a later change resolves. In such cases run ``git bisect skip`` and
go back to step 1.
”h]”hØ)”}”(hŒóNow build, install, and boot a kernel. This might fail for unrelated reasons,
for example, when a compile error happens at the current stage of the
bisection a later change resolves. In such cases run ``git bisect skip`` and
go back to step 1.”h]”(hŒÉNow build, install, and boot a kernel. This might fail for unrelated reasons,
for example, when a compile error happens at the current stage of the
bisection a later change resolves. In such cases run ”…””}”(hj§  hžhhŸNh Nubhâ)”}”(hŒ``git bisect skip``”h]”hŒgit bisect skip”…””}”(hj¯  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1háhj§  ubhŒ and
go back to step 1.”…””}”(hj§  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K.hj£  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j8  hjz  hžhhŸh³h Nubj9  )”}”(hXí  Check if the functionality that regressed works in the kernel you just built.

If it works, execute::

  git bisect good

If it is broken, run::

  git bisect bad

Note, getting this wrong just once will send the rest of the bisection
totally off course. To prevent having to start anew later you thus want to
ensure what you tell Git is correct; it is thus often wise to spend a few
minutes more on testing in case your reproducer is unreliable.

After issuing one of these two commands, Git will usually check out another
bisection point and print something like 'Bisecting: 675 revisions left to
test after this (roughly 10 steps)'. In that case go back to step 1.

If Git instead prints something like 'cafecaca0c0dacafecaca0c0dacafecaca0c0da
is the first bad commit', then you have finished the bisection. In that case
move to the next point below. Note, right after displaying that line Git will
show some details about the culprit including its patch description; this can
easily fill your terminal, so you might need to scroll up to see the message
mentioning the culprit's commit-id.

In case you missed Git's output, you can always run ``git bisect log`` to
print the status: it will show how many steps remain or mention the result of
the bisection.
”h]”(hØ)”}”(hŒMCheck if the functionality that regressed works in the kernel you just built.”h]”hŒMCheck if the functionality that regressed works in the kernel you just built.”…””}”(hjÑ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K3hjÍ  ubhØ)”}”(hŒIf it works, execute::”h]”hŒIf it works, execute:”…””}”(hjß  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K5hjÍ  ubjM  )”}”(hŒgit bisect good”h]”hŒgit bisect good”…””}”hjí  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h K7hjÍ  ubhØ)”}”(hŒIf it is broken, run::”h]”hŒIf it is broken, run:”…””}”(hjû  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K9hjÍ  ubjM  )”}”(hŒgit bisect bad”h]”hŒgit bisect bad”…””}”hj	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h K;hjÍ  ubhØ)”}”(hX  Note, getting this wrong just once will send the rest of the bisection
totally off course. To prevent having to start anew later you thus want to
ensure what you tell Git is correct; it is thus often wise to spend a few
minutes more on testing in case your reproducer is unreliable.”h]”hX  Note, getting this wrong just once will send the rest of the bisection
totally off course. To prevent having to start anew later you thus want to
ensure what you tell Git is correct; it is thus often wise to spend a few
minutes more on testing in case your reproducer is unreliable.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K=hjÍ  ubhØ)”}”(hŒÛAfter issuing one of these two commands, Git will usually check out another
bisection point and print something like 'Bisecting: 675 revisions left to
test after this (roughly 10 steps)'. In that case go back to step 1.”h]”hŒßAfter issuing one of these two commands, Git will usually check out another
bisection point and print something like â€˜Bisecting: 675 revisions left to
test after this (roughly 10 steps)â€™. In that case go back to step 1.”…””}”(hj%  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KBhjÍ  ubhØ)”}”(hX§  If Git instead prints something like 'cafecaca0c0dacafecaca0c0dacafecaca0c0da
is the first bad commit', then you have finished the bisection. In that case
move to the next point below. Note, right after displaying that line Git will
show some details about the culprit including its patch description; this can
easily fill your terminal, so you might need to scroll up to see the message
mentioning the culprit's commit-id.”h]”hX­  If Git instead prints something like â€˜cafecaca0c0dacafecaca0c0dacafecaca0c0da
is the first bad commitâ€™, then you have finished the bisection. In that case
move to the next point below. Note, right after displaying that line Git will
show some details about the culprit including its patch description; this can
easily fill your terminal, so you might need to scroll up to see the message
mentioning the culpritâ€™s commit-id.”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KFhjÍ  ubhØ)”}”(hŒ¦In case you missed Git's output, you can always run ``git bisect log`` to
print the status: it will show how many steps remain or mention the result of
the bisection.”h]”(hŒ6In case you missed Gitâ€™s output, you can always run ”…””}”(hjA  hžhhŸNh Nubhâ)”}”(hŒ``git bisect log``”h]”hŒgit bisect log”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1háhjA  ubhŒ` to
print the status: it will show how many steps remain or mention the result of
the bisection.”…””}”(hjA  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KMhjÍ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j8  hjz  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1jx  hj	  hžhhŸh³h K(ubj4  )”}”(hhh]”(j9  )”}”(hX  Recommended complementary task: put the bisection log and the current .config
file aside for the bug report; furthermore tell Git to reset the sources to
the state before the bisection::

   git bisect log > ~/bisection-log
   cp .config ~/bisection-config-culprit
   git bisect reset
”h]”(hØ)”}”(hŒºRecommended complementary task: put the bisection log and the current .config
file aside for the bug report; furthermore tell Git to reset the sources to
the state before the bisection::”h]”hŒ¹Recommended complementary task: put the bisection log and the current .config
file aside for the bug report; furthermore tell Git to reset the sources to
the state before the bisection:”…””}”(hjy  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KQhju  ubjM  )”}”(hŒWgit bisect log > ~/bisection-log
cp .config ~/bisection-config-culprit
git bisect reset”h]”hŒWgit bisect log > ~/bisection-log
cp .config ~/bisection-config-culprit
git bisect reset”…””}”hj‡  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h KUhju  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j8  hjr  hžhhŸh³h Nubj9  )”}”(hXZ  Recommended optional task: try reverting the culprit on top of the latest
codebase and check if that fixes your bug; if that is the case, it validates
the bisection and enables developers to resolve the regression through a
revert.

To try this, update your clone and check out latest mainline. Then tell Git
to revert the change by specifying its commit-id::

   git revert --no-edit cafec0cacaca0

Git might reject this, for example when the bisection landed on a merge
commit. In that case, abandon the attempt. Do the same, if Git fails to revert
the culprit on its own because later changes depend on it -- at least unless
you bisected a stable or longterm kernel series, in which case you want to
check out its latest codebase and try a revert there.

If a revert succeeds, build and test another kernel to check if reverting
resolved your regression.
”h]”(hØ)”}”(hŒçRecommended optional task: try reverting the culprit on top of the latest
codebase and check if that fixes your bug; if that is the case, it validates
the bisection and enables developers to resolve the regression through a
revert.”h]”hŒçRecommended optional task: try reverting the culprit on top of the latest
codebase and check if that fixes your bug; if that is the case, it validates
the bisection and enables developers to resolve the regression through a
revert.”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KYhj›  ubhØ)”}”(hŒ~To try this, update your clone and check out latest mainline. Then tell Git
to revert the change by specifying its commit-id::”h]”hŒ}To try this, update your clone and check out latest mainline. Then tell Git
to revert the change by specifying its commit-id:”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K^hj›  ubjM  )”}”(hŒ"git revert --no-edit cafec0cacaca0”h]”hŒ"git revert --no-edit cafec0cacaca0”…””}”hj»  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h Kahj›  ubhØ)”}”(hXd  Git might reject this, for example when the bisection landed on a merge
commit. In that case, abandon the attempt. Do the same, if Git fails to revert
the culprit on its own because later changes depend on it -- at least unless
you bisected a stable or longterm kernel series, in which case you want to
check out its latest codebase and try a revert there.”h]”hXd  Git might reject this, for example when the bisection landed on a merge
commit. In that case, abandon the attempt. Do the same, if Git fails to revert
the culprit on its own because later changes depend on it -- at least unless
you bisected a stable or longterm kernel series, in which case you want to
check out its latest codebase and try a revert there.”…””}”(hjÉ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kchj›  ubhØ)”}”(hŒcIf a revert succeeds, build and test another kernel to check if reverting
resolved your regression.”h]”hŒcIf a revert succeeds, build and test another kernel to check if reverting
resolved your regression.”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kihj›  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j8  hjr  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jv  jw  uh1j3  hŸh³h KQhj	  hžhubhØ)”}”(hŒ|With that the process is complete. Now report the regression as described by
Documentation/admin-guide/reporting-issues.rst.”h]”hŒ|With that the process is complete. Now report the regression as described by
Documentation/admin-guide/reporting-issues.rst.”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Klhj	  hžhubhÃ)”}”(hhh]”(hÈ)”}”(hŒBisecting linux-next”h]”hŒBisecting linux-next”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÿ  hžhhŸh³h KpubhØ)”}”(hŒÛIf you face a problem only happening in linux-next, bisect between the
linux-next branches 'stable' and 'master'. The following commands will start
the process for a linux-next tree you added as a remote called 'next'::”h]”hŒæIf you face a problem only happening in linux-next, bisect between the
linux-next branches â€˜stableâ€™ and â€˜masterâ€™. The following commands will start
the process for a linux-next tree you added as a remote called â€˜nextâ€™:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Krhjÿ  hžhubjM  )”}”(hŒGgit bisect start
git bisect good next/stable
git bisect bad next/master”h]”hŒGgit bisect start
git bisect good next/stable
git bisect bad next/master”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jL  hŸh³h Kvhjÿ  hžhubhØ)”}”(hŒéThe 'stable' branch refers to the state of linux-mainline that the current
linux-next release (found in the 'master' branch) is based on -- the former
thus should be free of any problems that show up in -next, but not in Linus'
tree.”h]”hŒóThe â€˜stableâ€™ branch refers to the state of linux-mainline that the current
linux-next release (found in the â€˜masterâ€™ branch) is based on -- the former
thus should be free of any problems that show up in -next, but not in Linusâ€™
tree.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kzhjÿ  hžhubhØ)”}”(hXO  This will bisect across a wide range of changes, some of which you might have
used in earlier linux-next releases without problems. Sadly there is no simple
way to avoid checking them: bisecting from one linux-next release to a later
one (say between 'next-20241020' and 'next-20241021') is impossible, as they
share no common history.”h]”hXW  This will bisect across a wide range of changes, some of which you might have
used in earlier linux-next releases without problems. Sadly there is no simple
way to avoid checking them: bisecting from one linux-next release to a later
one (say between â€˜next-20241020â€™ and â€˜next-20241021â€™) is impossible, as they
share no common history.”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khjÿ  hžhubeh}”(h]”Œbisecting-linux-next”ah ]”h"]”Œbisecting linux-next”ah$]”h&]”uh1hÂhj	  hžhhŸh³h KpubhÃ)”}”(hhh]”(hÈ)”}”(hŒAdditional reading material”h]”hŒAdditional reading material”…””}”(hjS  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjP  hžhhŸh³h K†ubj4  )”}”(hhh]”(j9  )”}”(hŒÀThe `man page for 'git bisect' <https://git-scm.com/docs/git-bisect>`_ and
`fighting regressions with 'git bisect' <https://git-scm.com/docs/git-bisect-lk2009.html>`_
in the Git documentation.”h]”hØ)”}”(hŒÀThe `man page for 'git bisect' <https://git-scm.com/docs/git-bisect>`_ and
`fighting regressions with 'git bisect' <https://git-scm.com/docs/git-bisect-lk2009.html>`_
in the Git documentation.”h]”(hŒThe ”…””}”(hjh  hžhhŸNh NubhŒ	reference”“”)”}”(hŒB`man page for 'git bisect' <https://git-scm.com/docs/git-bisect>`_”h]”hŒman page for â€˜git bisectâ€™”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œman page for 'git bisect'”Œrefuri”Œ#https://git-scm.com/docs/git-bisect”uh1jp  hjh  ubhŒtarget”“”)”}”(hŒ& <https://git-scm.com/docs/git-bisect>”h]”h}”(h]”Œman-page-for-git-bisect”ah ]”h"]”Œman page for 'git bisect'”ah$]”h&]”Œrefuri”jƒ  uh1j„  Œ
referenced”Khjh  ubhŒ and
”…””}”(hjh  hžhhŸNh Nubjq  )”}”(hŒ[`fighting regressions with 'git bisect' <https://git-scm.com/docs/git-bisect-lk2009.html>`_”h]”hŒ*fighting regressions with â€˜git bisectâ€™”…””}”(hj˜  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ&fighting regressions with 'git bisect'”j‚  Œ/https://git-scm.com/docs/git-bisect-lk2009.html”uh1jp  hjh  ubj…  )”}”(hŒ2 <https://git-scm.com/docs/git-bisect-lk2009.html>”h]”h}”(h]”Œ$fighting-regressions-with-git-bisect”ah ]”h"]”Œ&fighting regressions with 'git bisect'”ah$]”h&]”Œrefuri”j¨  uh1j„  j“  Khjh  ubhŒ
in the Git documentation.”…””}”(hjh  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kˆhjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j8  hja  hžhhŸh³h Nubj9  )”}”(hŒ}`Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_
from kernel developer Nathan Chancellor.”h]”hØ)”}”(hŒ}`Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_
from kernel developer Nathan Chancellor.”h]”(jq  )”}”(hŒT`Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_”h]”hŒWorking with git bisect”…””}”(hjÎ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒWorking with git bisect”j‚  Œ7https://nathanchance.dev/posts/working-with-git-bisect/”uh1jp  hjÊ  ubj…  )”}”(hŒ: <https://nathanchance.dev/posts/working-with-git-bisect/>”h]”h}”(h]”Œworking-with-git-bisect”ah ]”h"]”Œworking with git bisect”ah$]”h&]”Œrefuri”jÞ  uh1j„  j“  KhjÊ  ubhŒ)
from kernel developer Nathan Chancellor.”…””}”(hjÊ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K‹hjÆ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j8  hja  hžhhŸh³h Nubj9  )”}”(hŒ_`Using Git bisect to figure out when brokenness was introduced <http://webchick.net/node/99>`_.”h]”hØ)”}”(hjþ  h]”(jq  )”}”(hŒ^`Using Git bisect to figure out when brokenness was introduced <http://webchick.net/node/99>`_”h]”hŒ=Using Git bisect to figure out when brokenness was introduced”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ=Using Git bisect to figure out when brokenness was introduced”j‚  Œhttp://webchick.net/node/99”uh1jp  hj   ubj…  )”}”(hŒ <http://webchick.net/node/99>”h]”h}”(h]”Œ=using-git-bisect-to-figure-out-when-brokenness-was-introduced”ah ]”h"]”Œ=using git bisect to figure out when brokenness was introduced”ah$]”h&]”Œrefuri”j  uh1j„  j“  Khj   ubhŒ.”…””}”(hj   hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khjü  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j8  hja  hžhhŸh³h Nubj9  )”}”(hŒV`Fully automated bisecting with 'git bisect run' <https://lwn.net/Articles/317154>`_.
”h]”hØ)”}”(hŒU`Fully automated bisecting with 'git bisect run' <https://lwn.net/Articles/317154>`_.”h]”(jq  )”}”(hŒT`Fully automated bisecting with 'git bisect run' <https://lwn.net/Articles/317154>`_”h]”hŒ3Fully automated bisecting with â€˜git bisect runâ€™”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ/Fully automated bisecting with 'git bisect run'”j‚  Œhttps://lwn.net/Articles/317154”uh1jp  hj5  ubj…  )”}”(hŒ" <https://lwn.net/Articles/317154>”h]”h}”(h]”Œ-fully-automated-bisecting-with-git-bisect-run”ah ]”h"]”Œ/fully automated bisecting with 'git bisect run'”ah$]”h&]”Œrefuri”jI  uh1j„  j“  Khj5  ubhŒ.”…””}”(hj5  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KŽhj1  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j8  hja  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”jv  jw  uh1j3  hŸh³h KˆhjP  hžhubh¢)”}”(hŒend-of-content”h]”hŒend-of-content”…””}”hjm  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hjP  hžhhŸh³h K‘ubh¢)”}”(hXè  This document is maintained by Thorsten Leemhuis <linux@leemhuis.info>. If
you spot a typo or small mistake, feel free to let him know directly and
he'll fix it. You are free to do the same in a mostly informal way if you
want to contribute changes to the text -- but for copyright reasons please CC
linux-doc@vger.kernel.org and 'sign-off' your contribution as
Documentation/process/submitting-patches.rst explains in the section 'Sign
your work - the Developer's Certificate of Origin'.”h]”hXè  This document is maintained by Thorsten Leemhuis <linux@leemhuis.info>. If
you spot a typo or small mistake, feel free to let him know directly and
he'll fix it. You are free to do the same in a mostly informal way if you
want to contribute changes to the text -- but for copyright reasons please CC
linux-doc@vger.kernel.org and 'sign-off' your contribution as
Documentation/process/submitting-patches.rst explains in the section 'Sign
your work - the Developer's Certificate of Origin'.”…””}”hj{  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hjP  hžhhŸh³h K™ubh¢)”}”(hXe  This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
of the file. If you want to distribute this text under CC-BY-4.0 only,
please use 'The Linux kernel development community' for author attribution
and link this as source:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst”h]”hXe  This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
of the file. If you want to distribute this text under CC-BY-4.0 only,
please use 'The Linux kernel development community' for author attribution
and link this as source:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst”…””}”hj‰  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hjP  hžhhŸh³h K ubh¢)”}”(hX  Note: Only the content of this RST file as found in the Linux kernel sources
is available under CC-BY-4.0, as versions of this text that were processed
(for example by the kernel's build system) might contain content taken from
files which use a more restrictive license.”h]”hX  Note: Only the content of this RST file as found in the Linux kernel sources
is available under CC-BY-4.0, as versions of this text that were processed
(for example by the kernel's build system) might contain content taken from
files which use a more restrictive license.”…””}”hj—  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hjP  hžhhŸh³h K¥ubeh}”(h]”Œadditional-reading-material”ah ]”h"]”Œadditional reading material”ah$]”h&]”uh1hÂhj	  hžhhŸh³h K†ubeh}”(h]”Œ;finding-the-change-causing-a-kernel-issue-using-a-bisection”ah ]”h"]”Œ;finding the change causing a kernel issue using a bisection”ah$]”h&]”uh1hÂhhÄhžhhŸh³h Kubeh}”(h]”Œbisecting-a-regression”ah ]”h"]”Œbisecting a regression”ah$]”h&]”uh1hÂhhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÇNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jà  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jº  j·  j²  j¯  jM  jJ  jª  j§  j  jŒ  j²  j¯  jè  jå  j  j  jS  jP  uŒ	nametypes”}”(jº  ‰j²  ‰jM  ‰jª  ‰j  ˆj²  ˆjè  ˆj  ˆjS  ˆuh}”(j·  hÄj¯  j	  jJ  jÿ  j§  jP  jŒ  j†  j¯  j©  jå  jß  j  j  jP  jJ  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.