€•      Œ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”Œ5/translations/zh_CN/admin-guide/reporting-regressions”Œ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”Œ5/translations/zh_TW/admin-guide/reporting-regressions”Œ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”Œ5/translations/it_IT/admin-guide/reporting-regressions”Œ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”Œ5/translations/ja_JP/admin-guide/reporting-regressions”Œ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”Œ5/translations/ko_KR/admin-guide/reporting-regressions”Œ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”Œ5/translations/sp_SP/admin-guide/reporting-regressions”Œ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ŸŒO/var/lib/git/docbuild/linux/Documentation/admin-guide/reporting-regressions.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ŒReporting regressions”h]”hŒReporting regressions”…””}”(hhÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhhÄhžhhŸh³h KubhŒ	paragraph”“”)”}”(hŒ­"*We don't cause regressions*" is the first rule of Linux kernel development;
Linux founder and lead developer Linus Torvalds established it himself and
ensures it's obeyed.”h]”(hŒâ€œ”…””}”(hhÙhžhhŸNh NubhŒemphasis”“”)”}”(hŒ*We don't cause regressions*”h]”hŒWe donâ€™t cause regressions”…””}”(hhãhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1háhhÙubhŒ”â€ is the first rule of Linux kernel development;
Linux founder and lead developer Linus Torvalds established it himself and
ensures itâ€™s obeyed.”…””}”(hhÙhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hŒòThis document describes what the rule means for users and how the Linux kernel's
development model ensures to address all reported regressions; aspects relevant
for kernel developers are left to Documentation/process/handling-regressions.rst.”h]”hŒôThis document describes what the rule means for users and how the Linux kernelâ€™s
development model ensures to address all reported regressions; aspects relevant
for kernel developers are left to Documentation/process/handling-regressions.rst.”…””}”(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Œ The important bits (aka "TL;DR")”h]”hŒ$The important bits (aka â€œTL;DRâ€)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj	  hžhhŸh³h KubhŒenumerated_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hX  It's a regression if something running fine with one Linux kernel works worse
or not at all with a newer version. Note, the newer kernel has to be compiled
using a similar configuration; the detailed explanations below describes this
and other fine print in more detail.
”h]”hØ)”}”(hX  It's a regression if something running fine with one Linux kernel works worse
or not at all with a newer version. Note, the newer kernel has to be compiled
using a similar configuration; the detailed explanations below describes this
and other fine print in more detail.”h]”hX  Itâ€™s a regression if something running fine with one Linux kernel works worse
or not at all with a newer version. Note, the newer kernel has to be compiled
using a similar configuration; the detailed explanations below describes this
and other fine print in more detail.”…””}”(hj%  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj!  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  hžhhŸh³h Nubj   )”}”(hXu  Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
it already covers all aspects important for regressions and repeated
below for convenience. Two of them are important: start your report's subject
with "[REGRESSION]" and CC or forward it to `the regression mailing list
<https://lore.kernel.org/regressions/>`_ (regressions@lists.linux.dev).
”h]”hØ)”}”(hXt  Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
it already covers all aspects important for regressions and repeated
below for convenience. Two of them are important: start your report's subject
with "[REGRESSION]" and CC or forward it to `the regression mailing list
<https://lore.kernel.org/regressions/>`_ (regressions@lists.linux.dev).”h]”(hX  Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
it already covers all aspects important for regressions and repeated
below for convenience. Two of them are important: start your reportâ€™s subject
with â€œ[REGRESSION]â€ and CC or forward it to ”…””}”(hj=  hžhhŸNh NubhŒ	reference”“”)”}”(hŒE`the regression mailing list
<https://lore.kernel.org/regressions/>`_”h]”hŒthe regression mailing list”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œthe regression mailing list”Œrefuri”Œ$https://lore.kernel.org/regressions/”uh1jE  hj=  ubhŒtarget”“”)”}”(hŒ'
<https://lore.kernel.org/regressions/>”h]”h}”(h]”Œthe-regression-mailing-list”ah ]”h"]”Œthe regression mailing list”ah$]”h&]”Œrefuri”jX  uh1jY  Œ
referenced”Khj=  ubhŒ (”…””}”(hj=  hžhhŸNh NubjF  )”}”(hŒregressions@lists.linux.dev”h]”hŒregressions@lists.linux.dev”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:regressions@lists.linux.dev”uh1jE  hj=  ubhŒ).”…””}”(hj=  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj9  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  hžhhŸh³h Nubj   )”}”(hŒíOptional, but recommended: when sending or forwarding your report, make the
Linux kernel regression tracking bot "regzbot" track the issue by specifying
when the regression started like this::

    #regzbot introduced: v5.13..v5.14-rc1

”h]”(hØ)”}”(hŒÀOptional, but recommended: when sending or forwarding your report, make the
Linux kernel regression tracking bot "regzbot" track the issue by specifying
when the regression started like this::”h]”hŒÃOptional, but recommended: when sending or forwarding your report, make the
Linux kernel regression tracking bot â€œregzbotâ€ track the issue by specifying
when the regression started like this:”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj  ubhŒliteral_block”“”)”}”(hŒ%#regzbot introduced: v5.13..v5.14-rc1”h]”hŒ%#regzbot introduced: v5.13..v5.14-rc1”…””}”hj¡  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h K"hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1j  hj	  hžhhŸh³h Kubeh}”(h]”Œthe-important-bits-aka-tl-dr”ah ]”h"]”Œ the important bits (aka "tl;dr")”ah$]”h&]”uh1hÂhhÄhžhhŸh³h KubhÃ)”}”(hhh]”(hÈ)”}”(hŒ>All the details on Linux kernel regressions relevant for users”h]”hŒ>All the details on Linux kernel regressions relevant for users”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÈ  hžhhŸh³h K&ubhÃ)”}”(hhh]”(hÈ)”}”(hŒThe important basics”h]”hŒThe important basics”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÙ  hžhhŸh³h K*ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ=What is a "regression" and what is the "no regressions" rule?”h]”hŒEWhat is a â€œregressionâ€ and what is the â€œno regressionsâ€ rule?”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjê  hžhhŸh³h K.ubhØ)”}”(hXG  It's a regression if some application or practical use case running fine with
one Linux kernel works worse or not at all with a newer version compiled using a
similar configuration. The "no regressions" rule forbids this to take place; if
it happens by accident, developers that caused it are expected to quickly fix
the issue.”h]”hXM  Itâ€™s a regression if some application or practical use case running fine with
one Linux kernel works worse or not at all with a newer version compiled using a
similar configuration. The â€œno regressionsâ€ rule forbids this to take place; if
it happens by accident, developers that caused it are expected to quickly fix
the issue.”…””}”(hjû  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K0hjê  hžhubhØ)”}”(hXj  It thus is a regression when a WiFi driver from Linux 5.13 works fine, but with
5.14 doesn't work at all, works significantly slower, or misbehaves somehow.
It's also a regression if a perfectly working application suddenly shows erratic
behavior with a newer kernel version; such issues can be caused by changes in
procfs, sysfs, or one of the many other interfaces Linux provides to userland
software. But keep in mind, as mentioned earlier: 5.14 in this example needs to
be built from a configuration similar to the one from 5.13. This can be achieved
using ``make olddefconfig``, as explained in more detail below.”h]”(hX5  It thus is a regression when a WiFi driver from Linux 5.13 works fine, but with
5.14 doesnâ€™t work at all, works significantly slower, or misbehaves somehow.
Itâ€™s also a regression if a perfectly working application suddenly shows erratic
behavior with a newer kernel version; such issues can be caused by changes in
procfs, sysfs, or one of the many other interfaces Linux provides to userland
software. But keep in mind, as mentioned earlier: 5.14 in this example needs to
be built from a configuration similar to the one from 5.13. This can be achieved
using ”…””}”(hj	  hžhhŸNh NubhŒliteral”“”)”}”(hŒ``make olddefconfig``”h]”hŒmake olddefconfig”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj	  ubhŒ$, as explained in more detail below.”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K6hjê  hžhubhØ)”}”(hŒ÷Note the "practical use case" in the first sentence of this section: developers
despite the "no regressions" rule are free to change any aspect of the kernel
and even APIs or ABIs to userland, as long as no existing application or use
case breaks.”h]”hŒÿNote the â€œpractical use caseâ€ in the first sentence of this section: developers
despite the â€œno regressionsâ€ rule are free to change any aspect of the kernel
and even APIs or ABIs to userland, as long as no existing application or use
case breaks.”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K?hjê  hžhubhØ)”}”(hŒòAlso be aware the "no regressions" rule covers only interfaces the kernel
provides to the userland. It thus does not apply to kernel-internal interfaces
like the module API, which some externally developed drivers use to hook into
the kernel.”h]”hŒöAlso be aware the â€œno regressionsâ€ rule covers only interfaces the kernel
provides to the userland. It thus does not apply to kernel-internal interfaces
like the module API, which some externally developed drivers use to hook into
the kernel.”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KDhjê  hžhubeh}”(h]”Œ8what-is-a-regression-and-what-is-the-no-regressions-rule”ah ]”h"]”Œ=what is a "regression" and what is the "no regressions" rule?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h K.ubhÃ)”}”(hhh]”(hÈ)”}”(hŒHow do I report a regression?”h]”hŒHow do I report a regression?”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjO  hžhhŸh³h KJubhØ)”}”(hŒÍJust report the issue as outlined in
Documentation/admin-guide/reporting-issues.rst, it already describes the
important points. The following aspects outlined there are especially relevant
for regressions:”h]”hŒÍJust report the issue as outlined in
Documentation/admin-guide/reporting-issues.rst, it already describes the
important points. The following aspects outlined there are especially relevant
for regressions:”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KLhjO  hžhubhŒblock_quote”“”)”}”(hX×  * When checking for existing reports to join, also search the `archives of the
  Linux regressions mailing list <https://lore.kernel.org/regressions/>`_ and
  `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.

* Start your report's subject with "[REGRESSION]".

* In your report, clearly mention the last kernel version that worked fine and
  the first broken one. Ideally try to find the exact change causing the
  regression using a bisection, as explained below in more detail.

* Remember to let the Linux regressions mailing list
  (regressions@lists.linux.dev) know about your report:

  * If you report the regression by mail, CC the regressions list.

  * If you report your regression to some bug tracker, forward the submitted
    report by mail to the regressions list while CCing the maintainer and the
    mailing list for the subsystem in question.

  If it's a regression within a stable or longterm series (e.g.
  v5.15.3..v5.15.5), remember to CC the `Linux stable mailing list
  <https://lore.kernel.org/stable/>`_ (stable@vger.kernel.org).

 In case you performed a successful bisection, add everyone to the CC the
 culprit's commit message mentions in lines starting with "Signed-off-by:".
”h]”(hŒbullet_list”“”)”}”(hhh]”(j   )”}”(hŒèWhen checking for existing reports to join, also search the `archives of the
Linux regressions mailing list <https://lore.kernel.org/regressions/>`_ and
`regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
”h]”hØ)”}”(hŒçWhen checking for existing reports to join, also search the `archives of the
Linux regressions mailing list <https://lore.kernel.org/regressions/>`_ and
`regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.”h]”(hŒ<When checking for existing reports to join, also search the ”…””}”(hj}  hžhhŸNh NubjF  )”}”(hŒX`archives of the
Linux regressions mailing list <https://lore.kernel.org/regressions/>`_”h]”hŒ.archives of the
Linux regressions mailing list”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ.archives of the Linux regressions mailing list”jW  Œ$https://lore.kernel.org/regressions/”uh1jE  hj}  ubjZ  )”}”(hŒ' <https://lore.kernel.org/regressions/>”h]”h}”(h]”Œ.archives-of-the-linux-regressions-mailing-list”ah ]”h"]”Œ.archives of the linux regressions mailing list”ah$]”h&]”Œrefuri”j•  uh1jY  jh  Khj}  ubhŒ and
”…””}”(hj}  hžhhŸNh NubjF  )”}”(hŒM`regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_”h]”hŒregzbotâ€™s web-interface”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œregzbot's web-interface”jW  Œ0https://linux-regtracking.leemhuis.info/regzbot/”uh1jE  hj}  ubjZ  )”}”(hŒ3 <https://linux-regtracking.leemhuis.info/regzbot/>”h]”h}”(h]”Œregzbot-s-web-interface”ah ]”h"]”Œregzbot's web-interface”ah$]”h&]”Œrefuri”j·  uh1jY  jh  Khj}  ubhŒ.”…””}”(hj}  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KQhjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjv  ubj   )”}”(hŒ1Start your report's subject with "[REGRESSION]".
”h]”hØ)”}”(hŒ0Start your report's subject with "[REGRESSION]".”h]”hŒ6Start your reportâ€™s subject with â€œ[REGRESSION]â€.”…””}”(hjÙ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KUhjÕ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjv  ubj   )”}”(hŒÕIn your report, clearly mention the last kernel version that worked fine and
the first broken one. Ideally try to find the exact change causing the
regression using a bisection, as explained below in more detail.
”h]”hØ)”}”(hŒÔIn your report, clearly mention the last kernel version that worked fine and
the first broken one. Ideally try to find the exact change causing the
regression using a bisection, as explained below in more detail.”h]”hŒÔIn your report, clearly mention the last kernel version that worked fine and
the first broken one. Ideally try to find the exact change causing the
regression using a bisection, as explained below in more detail.”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KWhjí  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjv  ubj   )”}”(hX/  Remember to let the Linux regressions mailing list
(regressions@lists.linux.dev) know about your report:

* If you report the regression by mail, CC the regressions list.

* If you report your regression to some bug tracker, forward the submitted
  report by mail to the regressions list while CCing the maintainer and the
  mailing list for the subsystem in question.

If it's a regression within a stable or longterm series (e.g.
v5.15.3..v5.15.5), remember to CC the `Linux stable mailing list
<https://lore.kernel.org/stable/>`_ (stable@vger.kernel.org).
”h]”(hØ)”}”(hŒhRemember to let the Linux regressions mailing list
(regressions@lists.linux.dev) know about your report:”h]”(hŒ4Remember to let the Linux regressions mailing list
(”…””}”(hj	  hžhhŸNh NubjF  )”}”(hŒregressions@lists.linux.dev”h]”hŒregressions@lists.linux.dev”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:regressions@lists.linux.dev”uh1jE  hj	  ubhŒ) know about your report:”…””}”(hj	  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K[hj  ubju  )”}”(hhh]”(j   )”}”(hŒ?If you report the regression by mail, CC the regressions list.
”h]”hØ)”}”(hŒ>If you report the regression by mail, CC the regressions list.”h]”hŒ>If you report the regression by mail, CC the regressions list.”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K^hj.  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj+  ubj   )”}”(hŒ¿If you report your regression to some bug tracker, forward the submitted
report by mail to the regressions list while CCing the maintainer and the
mailing list for the subsystem in question.
”h]”hØ)”}”(hŒ¾If you report your regression to some bug tracker, forward the submitted
report by mail to the regressions list while CCing the maintainer and the
mailing list for the subsystem in question.”h]”hŒ¾If you report your regression to some bug tracker, forward the submitted
report by mail to the regressions list while CCing the maintainer and the
mailing list for the subsystem in question.”…””}”(hjJ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K`hjF  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj+  ubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1jt  hŸh³h K^hj  ubhØ)”}”(hŒ¼If it's a regression within a stable or longterm series (e.g.
v5.15.3..v5.15.5), remember to CC the `Linux stable mailing list
<https://lore.kernel.org/stable/>`_ (stable@vger.kernel.org).”h]”(hŒfIf itâ€™s a regression within a stable or longterm series (e.g.
v5.15.3..v5.15.5), remember to CC the ”…””}”(hjf  hžhhŸNh NubjF  )”}”(hŒ>`Linux stable mailing list
<https://lore.kernel.org/stable/>`_”h]”hŒLinux stable mailing list”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒLinux stable mailing list”jW  Œhttps://lore.kernel.org/stable/”uh1jE  hjf  ubjZ  )”}”(hŒ"
<https://lore.kernel.org/stable/>”h]”h}”(h]”Œlinux-stable-mailing-list”ah ]”h"]”Œlinux stable mailing list”ah$]”h&]”Œrefuri”j~  uh1jY  jh  Khjf  ubhŒ (”…””}”(hjf  hžhhŸNh NubjF  )”}”(hŒstable@vger.kernel.org”h]”hŒstable@vger.kernel.org”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:stable@vger.kernel.org”uh1jE  hjf  ubhŒ).”…””}”(hjf  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kdhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjv  ubeh}”(h]”h ]”h"]”h$]”h&]”jd  je  uh1jt  hŸh³h KQhjp  ubjo  )”}”(hŒ”In case you performed a successful bisection, add everyone to the CC the
culprit's commit message mentions in lines starting with "Signed-off-by:".
”h]”hØ)”}”(hŒ“In case you performed a successful bisection, add everyone to the CC the
culprit's commit message mentions in lines starting with "Signed-off-by:".”h]”hŒ™In case you performed a successful bisection, add everyone to the CC the
culpritâ€™s commit message mentions in lines starting with â€œSigned-off-by:â€.”…””}”(hjº  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khhj¶  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jn  hŸh³h Khhjp  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jn  hŸh³h KQhjO  hžhubhØ)”}”(hŒÐWhen CCing for forwarding your report to the list, consider directly telling the
aforementioned Linux kernel regression tracking bot about your report. To do
that, include a paragraph like this in your mail::”h]”hŒÏWhen CCing for forwarding your report to the list, consider directly telling the
aforementioned Linux kernel regression tracking bot about your report. To do
that, include a paragraph like this in your mail:”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KkhjO  hžhubj   )”}”(hŒ%#regzbot introduced: v5.13..v5.14-rc1”h]”hŒ%#regzbot introduced: v5.13..v5.14-rc1”…””}”hjâ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h KohjO  hžhubhØ)”}”(hXV  Regzbot will then consider your mail a report for a regression introduced in the
specified version range. In above case Linux v5.13 still worked fine and Linux
v5.14-rc1 was the first version where you encountered the issue. If you
performed a bisection to find the commit that caused the regression, specify the
culprit's commit-id instead::”h]”hXW  Regzbot will then consider your mail a report for a regression introduced in the
specified version range. In above case Linux v5.13 still worked fine and Linux
v5.14-rc1 was the first version where you encountered the issue. If you
performed a bisection to find the commit that caused the regression, specify the
culpritâ€™s commit-id instead:”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KqhjO  hžhubj   )”}”(hŒ#regzbot introduced: 1f2e3d4c5d”h]”hŒ#regzbot introduced: 1f2e3d4c5d”…””}”hjþ  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h KwhjO  hžhubhØ)”}”(hXŽ  Placing such a "regzbot command" is in your interest, as it will ensure the
report won't fall through the cracks unnoticed. If you omit this, the Linux
kernel's regressions tracker will take care of telling regzbot about your
regression, as long as you send a copy to the regressions mailing lists. But the
regression tracker is just one human which sometimes has to rest or occasionally
might even enjoy some time away from computers (as crazy as that might sound).
Relying on this person thus will result in an unnecessary delay before the
regressions becomes mentioned `on the list of tracked and unresolved Linux
kernel regressions <https://linux-regtracking.leemhuis.info/regzbot/>`_ and the
weekly regression reports sent by regzbot. Such delays can result in Linus
Torvalds being unaware of important regressions when deciding between "continue
development or call this finished and release the final?".”h]”(hXD  Placing such a â€œregzbot commandâ€ is in your interest, as it will ensure the
report wonâ€™t fall through the cracks unnoticed. If you omit this, the Linux
kernelâ€™s regressions tracker will take care of telling regzbot about your
regression, as long as you send a copy to the regressions mailing lists. But the
regression tracker is just one human which sometimes has to rest or occasionally
might even enjoy some time away from computers (as crazy as that might sound).
Relying on this person thus will result in an unnecessary delay before the
regressions becomes mentioned ”…””}”(hj  hžhhŸNh NubjF  )”}”(hŒt`on the list of tracked and unresolved Linux
kernel regressions <https://linux-regtracking.leemhuis.info/regzbot/>`_”h]”hŒ>on the list of tracked and unresolved Linux
kernel regressions”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ>on the list of tracked and unresolved Linux kernel regressions”jW  Œ0https://linux-regtracking.leemhuis.info/regzbot/”uh1jE  hj  ubjZ  )”}”(hŒ3 <https://linux-regtracking.leemhuis.info/regzbot/>”h]”h}”(h]”Œ>on-the-list-of-tracked-and-unresolved-linux-kernel-regressions”ah ]”h"]”Œ>on the list of tracked and unresolved linux kernel regressions”ah$]”h&]”Œrefuri”j$  uh1jY  jh  Khj  ubhŒâ and the
weekly regression reports sent by regzbot. Such delays can result in Linus
Torvalds being unaware of important regressions when deciding between â€œcontinue
development or call this finished and release the final?â€.”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KyhjO  hžhubeh}”(h]”Œhow-do-i-report-a-regression”ah ]”h"]”Œhow do i report a regression?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h KJubhÃ)”}”(hhh]”(hÈ)”}”(hŒ!Are really all regressions fixed?”h]”hŒ!Are really all regressions fixed?”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjD  hžhhŸh³h K‡ubhØ)”}”(hŒ¸Nearly all of them are, as long as the change causing the regression (the
"culprit commit") is reliably identified. Some regressions can be fixed without
this, but often it's required.”h]”hŒ¾Nearly all of them are, as long as the change causing the regression (the
â€œculprit commitâ€) is reliably identified. Some regressions can be fixed without
this, but often itâ€™s required.”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K‰hjD  hžhubeh}”(h]”Œ are-really-all-regressions-fixed”ah ]”h"]”Œ!are really all regressions fixed?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h K‡ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ1Who needs to find the root cause of a regression?”h]”hŒ1Who needs to find the root cause of a regression?”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjk  hžhhŸh³h KŽubhØ)”}”(hX£  Developers of the affected code area should try to locate the culprit on their
own. But for them that's often impossible to do with reasonable effort, as quite
a lot of issues only occur in a particular environment outside the developer's
reach -- for example, a specific hardware platform, firmware, Linux distro,
system's configuration, or application. That's why in the end it's often up to
the reporter to locate the culprit commit; sometimes users might even need to
run additional tests afterwards to pinpoint the exact root cause. Developers
should offer advice and reasonably help where they can, to make this process
relatively easy and achievable for typical users.”h]”hX­  Developers of the affected code area should try to locate the culprit on their
own. But for them thatâ€™s often impossible to do with reasonable effort, as quite
a lot of issues only occur in a particular environment outside the developerâ€™s
reach -- for example, a specific hardware platform, firmware, Linux distro,
systemâ€™s configuration, or application. Thatâ€™s why in the end itâ€™s often up to
the reporter to locate the culprit commit; sometimes users might even need to
run additional tests afterwards to pinpoint the exact root cause. Developers
should offer advice and reasonably help where they can, to make this process
relatively easy and achievable for typical users.”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khjk  hžhubeh}”(h]”Œ0who-needs-to-find-the-root-cause-of-a-regression”ah ]”h"]”Œ1who needs to find the root cause of a regression?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h KŽubhÃ)”}”(hhh]”(hÈ)”}”(hŒHow can I find the culprit?”h]”hŒHow can I find the culprit?”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj’  hžhhŸh³h K›ubhØ)”}”(hX—  Perform a bisection, as roughly outlined in
Documentation/admin-guide/reporting-issues.rst and described in more detail by
Documentation/admin-guide/bug-bisect.rst. It might sound like a lot of work, but
in many cases finds the culprit relatively quickly. If it's hard or
time-consuming to reliably reproduce the issue, consider teaming up with other
affected users to narrow down the search range together.”h]”hX™  Perform a bisection, as roughly outlined in
Documentation/admin-guide/reporting-issues.rst and described in more detail by
Documentation/admin-guide/bug-bisect.rst. It might sound like a lot of work, but
in many cases finds the culprit relatively quickly. If itâ€™s hard or
time-consuming to reliably reproduce the issue, consider teaming up with other
affected users to narrow down the search range together.”…””}”(hj£  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khj’  hžhubeh}”(h]”Œhow-can-i-find-the-culprit”ah ]”h"]”Œhow can i find the culprit?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h K›ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ6Who can I ask for advice when it comes to regressions?”h]”hŒ6Who can I ask for advice when it comes to regressions?”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj¹  hžhhŸh³h K¥ubhØ)”}”(hŒèSend a mail to the regressions mailing list (regressions@lists.linux.dev) while
CCing the Linux kernel's regression tracker (regressions@leemhuis.info); if the
issue might better be dealt with in private, feel free to omit the list.”h]”(hŒ-Send a mail to the regressions mailing list (”…””}”(hjÊ  hžhhŸNh NubjF  )”}”(hŒregressions@lists.linux.dev”h]”hŒregressions@lists.linux.dev”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ"mailto:regressions@lists.linux.dev”uh1jE  hjÊ  ubhŒ7) while
CCing the Linux kernelâ€™s regression tracker (”…””}”(hjÊ  hžhhŸNh NubjF  )”}”(hŒregressions@leemhuis.info”h]”hŒregressions@leemhuis.info”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ mailto:regressions@leemhuis.info”uh1jE  hjÊ  ubhŒR); if the
issue might better be dealt with in private, feel free to omit the list.”…””}”(hjÊ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K§hj¹  hžhubeh}”(h]”Œ5who-can-i-ask-for-advice-when-it-comes-to-regressions”ah ]”h"]”Œ6who can i ask for advice when it comes to regressions?”ah$]”h&]”uh1hÂhjÙ  hžhhŸh³h K¥ubeh}”(h]”Œthe-important-basics”ah ]”h"]”Œthe important basics”ah$]”h&]”uh1hÂhjÈ  hžhhŸh³h K*ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ$Additional details about regressions”h]”hŒ$Additional details about regressions”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj  hžhhŸh³h K­ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ.What is the goal of the "no regressions" rule?”h]”hŒ2What is the goal of the â€œno regressionsâ€ rule?”…””}”(hj$  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj!  hžhhŸh³h K±ubhØ)”}”(hX+  Users should feel safe when updating kernel versions and not have to worry
something might break. This is in the interest of the kernel developers to make
updating attractive: they don't want users to stay on stable or longterm Linux
series that are either abandoned or more than one and a half years old. That's
in everybody's interest, as `those series might have known bugs, security
issues, or other problematic aspects already fixed in later versions
<http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>`_.
Additionally, the kernel developers want to make it simple and appealing for
users to test the latest pre-release or regular release. That's also in
everybody's interest, as it's a lot easier to track down and fix problems, if
they are reported shortly after being introduced.”h]”(hX[  Users should feel safe when updating kernel versions and not have to worry
something might break. This is in the interest of the kernel developers to make
updating attractive: they donâ€™t want users to stay on stable or longterm Linux
series that are either abandoned or more than one and a half years old. Thatâ€™s
in everybodyâ€™s interest, as ”…””}”(hj2  hžhhŸNh NubjF  )”}”(hŒÀ`those series might have known bugs, security
issues, or other problematic aspects already fixed in later versions
<http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>`_”h]”hŒqthose series might have known bugs, security
issues, or other problematic aspects already fixed in later versions”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œqthose series might have known bugs, security issues, or other problematic aspects already fixed in later versions”jW  ŒIhttp://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/”uh1jE  hj2  ubjZ  )”}”(hŒL
<http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/>”h]”h}”(h]”Œothose-series-might-have-known-bugs-security-issues-or-other-problematic-aspects-already-fixed-in-later-versions”ah ]”h"]”Œqthose series might have known bugs, security issues, or other problematic aspects already fixed in later versions”ah$]”h&]”Œrefuri”jJ  uh1jY  jh  Khj2  ubhX  .
Additionally, the kernel developers want to make it simple and appealing for
users to test the latest pre-release or regular release. Thatâ€™s also in
everybodyâ€™s interest, as itâ€™s a lot easier to track down and fix problems, if
they are reported shortly after being introduced.”…””}”(hj2  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K³hj!  hžhubeh}”(h]”Œ+what-is-the-goal-of-the-no-regressions-rule”ah ]”h"]”Œ.what is the goal of the "no regressions" rule?”ah$]”h&]”uh1hÂhj  hžhhŸh³h K±ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ8Is the "no regressions" rule really adhered in practice?”h]”hŒ<Is the â€œno regressionsâ€ rule really adhered in practice?”…””}”(hjm  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjj  hžhhŸh³h KÀubhØ)”}”(hŒÈIt's taken really seriously, as can be seen by many mailing list posts from
Linux creator and lead developer Linus Torvalds, some of which are quoted in
Documentation/process/handling-regressions.rst.”h]”hŒÊItâ€™s taken really seriously, as can be seen by many mailing list posts from
Linux creator and lead developer Linus Torvalds, some of which are quoted in
Documentation/process/handling-regressions.rst.”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÂhjj  hžhubhØ)”}”(hŒ­Exceptions to this rule are extremely rare; in the past developers almost always
turned out to be wrong when they assumed a particular situation was warranting
an exception.”h]”hŒ­Exceptions to this rule are extremely rare; in the past developers almost always
turned out to be wrong when they assumed a particular situation was warranting
an exception.”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÆhjj  hžhubeh}”(h]”Œ5is-the-no-regressions-rule-really-adhered-in-practice”ah ]”h"]”Œ8is the "no regressions" rule really adhered in practice?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KÀubhÃ)”}”(hhh]”(hÈ)”}”(hŒ;Who ensures the "no regressions" rule is actually followed?”h]”hŒ?Who ensures the â€œno regressionsâ€ rule is actually followed?”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjŸ  hžhhŸh³h KËubhØ)”}”(hŒÑThe subsystem maintainers should take care of that, which are watched and
supported by the tree maintainers -- e.g. Linus Torvalds for mainline and
Greg Kroah-Hartman et al. for various stable/longterm series.”h]”hŒÑThe subsystem maintainers should take care of that, which are watched and
supported by the tree maintainers -- e.g. Linus Torvalds for mainline and
Greg Kroah-Hartman et al. for various stable/longterm series.”…””}”(hj°  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÍhjŸ  hžhubhØ)”}”(hXõ  All of them are helped by people trying to ensure no regression report falls
through the cracks. One of them is Thorsten Leemhuis, who's currently acting as
the Linux kernel's "regressions tracker"; to facilitate this work he relies on
regzbot, the Linux kernel regression tracking bot. That's why you want to bring
your report on the radar of these people by CCing or forwarding each report to
the regressions mailing list, ideally with a "regzbot command" in your mail to
get it tracked immediately.”h]”hX  All of them are helped by people trying to ensure no regression report falls
through the cracks. One of them is Thorsten Leemhuis, whoâ€™s currently acting as
the Linux kernelâ€™s â€œregressions trackerâ€; to facilitate this work he relies on
regzbot, the Linux kernel regression tracking bot. Thatâ€™s why you want to bring
your report on the radar of these people by CCing or forwarding each report to
the regressions mailing list, ideally with a â€œregzbot commandâ€ in your mail to
get it tracked immediately.”…””}”(hj¾  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÑhjŸ  hžhubeh}”(h]”Œ8who-ensures-the-no-regressions-rule-is-actually-followed”ah ]”h"]”Œ;who ensures the "no regressions" rule is actually followed?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KËubhÃ)”}”(hhh]”(hÈ)”}”(hŒ+How quickly are regressions normally fixed?”h]”hŒ+How quickly are regressions normally fixed?”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÔ  hžhhŸh³h KÚubhØ)”}”(hX+  Developers should fix any reported regression as quickly as possible, to provide
affected users with a solution in a timely manner and prevent more users from
running into the issue; nevertheless developers need to take enough time and
care to ensure regression fixes do not cause additional damage.”h]”hX+  Developers should fix any reported regression as quickly as possible, to provide
affected users with a solution in a timely manner and prevent more users from
running into the issue; nevertheless developers need to take enough time and
care to ensure regression fixes do not cause additional damage.”…””}”(hjå  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KÜhjÔ  hžhubhØ)”}”(hŒÂThe answer thus depends on various factors like the impact of a regression, its
age, or the Linux series in which it occurs. In the end though, most regressions
should be fixed within two weeks.”h]”hŒÂThe answer thus depends on various factors like the impact of a regression, its
age, or the Linux series in which it occurs. In the end though, most regressions
should be fixed within two weeks.”…””}”(hjó  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KáhjÔ  hžhubeh}”(h]”Œ*how-quickly-are-regressions-normally-fixed”ah ]”h"]”Œ+how quickly are regressions normally fixed?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KÚubhÃ)”}”(hhh]”(hÈ)”}”(hŒJIs it a regression, if the issue can be avoided by updating some software?”h]”hŒJIs it a regression, if the issue can be avoided by updating some software?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj	  hžhhŸh³h KæubhØ)”}”(hŒpAlmost always: yes. If a developer tells you otherwise, ask the regression
tracker for advice as outlined above.”h]”hŒpAlmost always: yes. If a developer tells you otherwise, ask the regression
tracker for advice as outlined above.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kèhj	  hžhubeh}”(h]”ŒHis-it-a-regression-if-the-issue-can-be-avoided-by-updating-some-software”ah ]”h"]”ŒJis it a regression, if the issue can be avoided by updating some software?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KæubhÃ)”}”(hhh]”(hÈ)”}”(hŒKIs it a regression, if a newer kernel works slower or consumes more energy?”h]”hŒKIs it a regression, if a newer kernel works slower or consumes more energy?”…””}”(hj3  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj0  hžhhŸh³h KìubhØ)”}”(hŒùYes, but the difference has to be significant. A five percent slow-down in a
micro-benchmark thus is unlikely to qualify as regression, unless it also
influences the results of a broad benchmark by more than one percent. If in
doubt, ask for advice.”h]”hŒùYes, but the difference has to be significant. A five percent slow-down in a
micro-benchmark thus is unlikely to qualify as regression, unless it also
influences the results of a broad benchmark by more than one percent. If in
doubt, ask for advice.”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kîhj0  hžhubeh}”(h]”ŒIis-it-a-regression-if-a-newer-kernel-works-slower-or-consumes-more-energy”ah ]”h"]”ŒKis it a regression, if a newer kernel works slower or consumes more energy?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KìubhÃ)”}”(hhh]”(hÈ)”}”(hŒLIs it a regression, if an external kernel module breaks when updating Linux?”h]”hŒLIs it a regression, if an external kernel module breaks when updating Linux?”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjW  hžhhŸh³h KôubhØ)”}”(hX   No, as the "no regression" rule is about interfaces and services the Linux
kernel provides to the userland. It thus does not cover building or running
externally developed kernel modules, as they run in kernel-space and hook into
the kernel using internal interfaces occasionally changed.”h]”hX$  No, as the â€œno regressionâ€ rule is about interfaces and services the Linux
kernel provides to the userland. It thus does not cover building or running
externally developed kernel modules, as they run in kernel-space and hook into
the kernel using internal interfaces occasionally changed.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KöhjW  hžhubeh}”(h]”ŒJis-it-a-regression-if-an-external-kernel-module-breaks-when-updating-linux”ah ]”h"]”ŒLis it a regression, if an external kernel module breaks when updating linux?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KôubhÃ)”}”(hhh]”(hÈ)”}”(hŒ>How are regressions handled that are caused by security fixes?”h]”hŒ>How are regressions handled that are caused by security fixes?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj~  hžhhŸh³h KüubhØ)”}”(hXZ  In extremely rare situations security issues can't be fixed without causing
regressions; those fixes are given way, as they are the lesser evil in the end.
Luckily this middling almost always can be avoided, as key developers for the
affected area and often Linus Torvalds himself try very hard to fix security
issues without causing regressions.”h]”hX\  In extremely rare situations security issues canâ€™t be fixed without causing
regressions; those fixes are given way, as they are the lesser evil in the end.
Luckily this middling almost always can be avoided, as key developers for the
affected area and often Linus Torvalds himself try very hard to fix security
issues without causing regressions.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kþhj~  hžhubhØ)”}”(hŒ»If you nevertheless face such a case, check the mailing list archives if people
tried their best to avoid the regression. If not, report it; if in doubt, ask
for advice as outlined above.”h]”hŒ»If you nevertheless face such a case, check the mailing list archives if people
tried their best to avoid the regression. If not, report it; if in doubt, ask
for advice as outlined above.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj~  hžhubeh}”(h]”Œ=how-are-regressions-handled-that-are-caused-by-security-fixes”ah ]”h"]”Œ>how are regressions handled that are caused by security fixes?”ah$]”h&]”uh1hÂhj  hžhhŸh³h KüubhÃ)”}”(hhh]”(hÈ)”}”(hŒJWhat happens if fixing a regression is impossible without causing another?”h]”hŒJWhat happens if fixing a regression is impossible without causing another?”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj³  hžhhŸh³h M	ubhØ)”}”(hX’  Sadly these things happen, but luckily not very often; if they occur, expert
developers of the affected code area should look into the issue to find a fix
that avoids regressions or at least their impact. If you run into such a
situation, do what was outlined already for regressions caused by security
fixes: check earlier discussions if people already tried their best and ask for
advice if in doubt.”h]”hX’  Sadly these things happen, but luckily not very often; if they occur, expert
developers of the affected code area should look into the issue to find a fix
that avoids regressions or at least their impact. If you run into such a
situation, do what was outlined already for regressions caused by security
fixes: check earlier discussions if people already tried their best and ask for
advice if in doubt.”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj³  hžhubhØ)”}”(hX  A quick note while at it: these situations could be avoided, if people would
regularly give mainline pre-releases (say v5.15-rc1 or -rc3) from each
development cycle a test run. This is best explained by imagining a change
integrated between Linux v5.14 and v5.15-rc1 which causes a regression, but at
the same time is a hard requirement for some other improvement applied for
5.15-rc1. All these changes often can simply be reverted and the regression thus
solved, if someone finds and reports it before 5.15 is released. A few days or
weeks later this solution can become impossible, as some software might have
started to rely on aspects introduced by one of the follow-up changes: reverting
all changes would then cause a regression for users of said software and thus is
out of the question.”h]”hX  A quick note while at it: these situations could be avoided, if people would
regularly give mainline pre-releases (say v5.15-rc1 or -rc3) from each
development cycle a test run. This is best explained by imagining a change
integrated between Linux v5.14 and v5.15-rc1 which causes a regression, but at
the same time is a hard requirement for some other improvement applied for
5.15-rc1. All these changes often can simply be reverted and the regression thus
solved, if someone finds and reports it before 5.15 is released. A few days or
weeks later this solution can become impossible, as some software might have
started to rely on aspects introduced by one of the follow-up changes: reverting
all changes would then cause a regression for users of said software and thus is
out of the question.”…””}”(hjÒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj³  hžhubeh}”(h]”ŒIwhat-happens-if-fixing-a-regression-is-impossible-without-causing-another”ah ]”h"]”ŒJwhat happens if fixing a regression is impossible without causing another?”ah$]”h&]”uh1hÂhj  hžhhŸh³h M	ubhÃ)”}”(hhh]”(hÈ)”}”(hŒGIs it a regression, if some feature I relied on was removed months ago?”h]”hŒGIs it a regression, if some feature I relied on was removed months ago?”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjè  hžhhŸh³h MubhØ)”}”(hX  It is, but often it's hard to fix such regressions due to the aspects outlined
in the previous section. It hence needs to be dealt with on a case-by-case
basis. This is another reason why it's in everybody's interest to regularly test
mainline pre-releases.”h]”hX  It is, but often itâ€™s hard to fix such regressions due to the aspects outlined
in the previous section. It hence needs to be dealt with on a case-by-case
basis. This is another reason why itâ€™s in everybodyâ€™s interest to regularly test
mainline pre-releases.”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M!hjè  hžhubeh}”(h]”ŒEis-it-a-regression-if-some-feature-i-relied-on-was-removed-months-ago”ah ]”h"]”ŒGis it a regression, if some feature i relied on was removed months ago?”ah$]”h&]”uh1hÂhj  hžhhŸh³h MubhÃ)”}”(hhh]”(hÈ)”}”(hŒMDoes the "no regression" rule apply if I seem to be the only affected person?”h]”hŒQDoes the â€œno regressionâ€ rule apply if I seem to be the only affected person?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj  hžhhŸh³h M'ubhØ)”}”(hŒšIt does, but only for practical usage: the Linux developers want to be free to
remove support for hardware only to be found in attics and museums anymore.”h]”hŒšIt does, but only for practical usage: the Linux developers want to be free to
remove support for hardware only to be found in attics and museums anymore.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M)hj  hžhubhØ)”}”(hXÈ  Note, sometimes regressions can't be avoided to make progress -- and the latter
is needed to prevent Linux from stagnation. Hence, if only very few users seem
to be affected by a regression, it for the greater good might be in their and
everyone else's interest to lettings things pass. Especially if there is an
easy way to circumvent the regression somehow, for example by updating some
software or using a kernel parameter created just for this purpose.”h]”hXÌ  Note, sometimes regressions canâ€™t be avoided to make progress -- and the latter
is needed to prevent Linux from stagnation. Hence, if only very few users seem
to be affected by a regression, it for the greater good might be in their and
everyone elseâ€™s interest to lettings things pass. Especially if there is an
easy way to circumvent the regression somehow, for example by updating some
software or using a kernel parameter created just for this purpose.”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M,hj  hžhubeh}”(h]”ŒJdoes-the-no-regression-rule-apply-if-i-seem-to-be-the-only-affected-person”ah ]”h"]”ŒMdoes the "no regression" rule apply if i seem to be the only affected person?”ah$]”h&]”uh1hÂhj  hžhhŸh³h M'ubhÃ)”}”(hhh]”(hÈ)”}”(hŒDDoes the regression rule apply for code in the staging tree as well?”h]”hŒDDoes the regression rule apply for code in the staging tree as well?”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjD  hžhhŸh³h M4ubhØ)”}”(hŒßNot according to the `help text for the configuration option covering all
staging code <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/Kconfig>`_,
which since its early days states::”h]”(hŒNot according to the ”…””}”(hjU  hžhhŸNh NubjF  )”}”(hŒ¥`help text for the configuration option covering all
staging code <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/Kconfig>`_”h]”hŒ@help text for the configuration option covering all
staging code”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œ@help text for the configuration option covering all staging code”jW  Œ_https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/Kconfig”uh1jE  hjU  ubjZ  )”}”(hŒb <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/staging/Kconfig>”h]”h}”(h]”Œ@help-text-for-the-configuration-option-covering-all-staging-code”ah ]”h"]”Œ@help text for the configuration option covering all staging code”ah$]”h&]”Œrefuri”jm  uh1jY  jh  KhjU  ubhŒ$,
which since its early days states:”…””}”(hjU  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M6hjD  hžhubj   )”}”(hŒªPlease note that these drivers are under heavy development, may or
may not work, and may contain userspace interfaces that most likely
will be changed in the near future.”h]”hŒªPlease note that these drivers are under heavy development, may or
may not work, and may contain userspace interfaces that most likely
will be changed in the near future.”…””}”hj…  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h M:hjD  hžhubhØ)”}”(hX/  The staging developers nevertheless often adhere to the "no regressions" rule,
but sometimes bend it to make progress. That's for example why some users had to
deal with (often negligible) regressions when a WiFi driver from the staging
tree was replaced by a totally different one written from scratch.”h]”hX5  The staging developers nevertheless often adhere to the â€œno regressionsâ€ rule,
but sometimes bend it to make progress. Thatâ€™s for example why some users had to
deal with (often negligible) regressions when a WiFi driver from the staging
tree was replaced by a totally different one written from scratch.”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M>hjD  hžhubeh}”(h]”ŒCdoes-the-regression-rule-apply-for-code-in-the-staging-tree-as-well”ah ]”h"]”ŒDdoes the regression rule apply for code in the staging tree as well?”ah$]”h&]”uh1hÂhj  hžhhŸh³h M4ubhÃ)”}”(hhh]”(hÈ)”}”(hŒIWhy do later versions have to be "compiled with a similar configuration"?”h]”hŒMWhy do later versions have to be â€œcompiled with a similar configurationâ€?”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj©  hžhhŸh³h MDubhØ)”}”(hX  Because the Linux kernel developers sometimes integrate changes known to cause
regressions, but make them optional and disable them in the kernel's default
configuration. This trick allows progress, as the "no regressions" rule
otherwise would lead to stagnation.”h]”hX  Because the Linux kernel developers sometimes integrate changes known to cause
regressions, but make them optional and disable them in the kernelâ€™s default
configuration. This trick allows progress, as the â€œno regressionsâ€ rule
otherwise would lead to stagnation.”…””}”(hjº  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MFhj©  hžhubhØ)”}”(hXo  Consider for example a new security feature blocking access to some kernel
interfaces often abused by malware, which at the same time are required to run a
few rarely used applications. The outlined approach makes both camps happy:
people using these applications can leave the new security feature off, while
everyone else can enable it without running into trouble.”h]”hXo  Consider for example a new security feature blocking access to some kernel
interfaces often abused by malware, which at the same time are required to run a
few rarely used applications. The outlined approach makes both camps happy:
people using these applications can leave the new security feature off, while
everyone else can enable it without running into trouble.”…””}”(hjÈ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MKhj©  hžhubeh}”(h]”ŒFwhy-do-later-versions-have-to-be-compiled-with-a-similar-configuration”ah ]”h"]”ŒIwhy do later versions have to be "compiled with a similar configuration"?”ah$]”h&]”uh1hÂhj  hžhhŸh³h MDubhÃ)”}”(hhh]”(hÈ)”}”(hŒDHow to create a configuration similar to the one of an older kernel?”h]”hŒDHow to create a configuration similar to the one of an older kernel?”…””}”(hjá  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÞ  hžhhŸh³h MRubhØ)”}”(hX›  Start your machine with a known-good kernel and configure the newer Linux
version with ``make olddefconfig``. This makes the kernel's build scripts pick
up the configuration file (the ".config" file) from the running kernel as base
for the new one you are about to compile; afterwards they set all new
configuration options to their default value, which should disable new features
that might cause regressions.”h]”(hŒWStart your machine with a known-good kernel and configure the newer Linux
version with ”…””}”(hjï  hžhhŸNh Nubj  )”}”(hŒ``make olddefconfig``”h]”hŒmake olddefconfig”…””}”(hj÷  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hjï  ubhX5  . This makes the kernelâ€™s build scripts pick
up the configuration file (the â€œ.configâ€ file) from the running kernel as base
for the new one you are about to compile; afterwards they set all new
configuration options to their default value, which should disable new features
that might cause regressions.”…””}”(hjï  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MThjÞ  hžhubeh}”(h]”ŒChow-to-create-a-configuration-similar-to-the-one-of-an-older-kernel”ah ]”h"]”ŒDhow to create a configuration similar to the one of an older kernel?”ah$]”h&]”uh1hÂhj  hžhhŸh³h MRubhÃ)”}”(hhh]”(hÈ)”}”(hŒDCan I report a regression I found with pre-compiled vanilla kernels?”h]”hŒDCan I report a regression I found with pre-compiled vanilla kernels?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj  hžhhŸh³h M\ubhØ)”}”(hX$  You need to ensure the newer kernel was compiled with a similar configuration
file as the older one (see above), as those that built them might have enabled
some known-to-be incompatible feature for the newer kernel. If in doubt, report
the matter to the kernel's provider and ask for advice.”h]”hX&  You need to ensure the newer kernel was compiled with a similar configuration
file as the older one (see above), as those that built them might have enabled
some known-to-be incompatible feature for the newer kernel. If in doubt, report
the matter to the kernelâ€™s provider and ask for advice.”…””}”(hj(  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M^hj  hžhubeh}”(h]”ŒCcan-i-report-a-regression-i-found-with-pre-compiled-vanilla-kernels”ah ]”h"]”ŒDcan i report a regression i found with pre-compiled vanilla kernels?”ah$]”h&]”uh1hÂhj  hžhhŸh³h M\ubeh}”(h]”Œ$additional-details-about-regressions”ah ]”h"]”Œ$additional details about regressions”ah$]”h&]”uh1hÂhjÈ  hžhhŸh³h K­ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ-More about regression tracking with "regzbot"”h]”hŒ1More about regression tracking with â€œregzbotâ€”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjF  hžhhŸh³h MeubhÃ)”}”(hhh]”(hÈ)”}”(hŒ;What is regression tracking and why should I care about it?”h]”hŒ;What is regression tracking and why should I care about it?”…””}”(hjZ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjW  hžhhŸh³h MhubhØ)”}”(hXÐ  Rules like "no regressions" need someone to ensure they are followed, otherwise
they are broken either accidentally or on purpose. History has shown this to be
true for Linux kernel development as well. That's why Thorsten Leemhuis, the
Linux Kernel's regression tracker, and some people try to ensure all regression
are fixed by keeping an eye on them until they are resolved. Neither of them are
paid for this, that's why the work is done on a best effort basis.”h]”hXÚ  Rules like â€œno regressionsâ€ need someone to ensure they are followed, otherwise
they are broken either accidentally or on purpose. History has shown this to be
true for Linux kernel development as well. Thatâ€™s why Thorsten Leemhuis, the
Linux Kernelâ€™s regression tracker, and some people try to ensure all regression
are fixed by keeping an eye on them until they are resolved. Neither of them are
paid for this, thatâ€™s why the work is done on a best effort basis.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h MjhjW  hžhubeh}”(h]”Œ:what-is-regression-tracking-and-why-should-i-care-about-it”ah ]”h"]”Œ;what is regression tracking and why should i care about it?”ah$]”h&]”uh1hÂhjF  hžhhŸh³h MhubhÃ)”}”(hhh]”(hÈ)”}”(hŒ=Why and how are Linux kernel regressions tracked using a bot?”h]”hŒ=Why and how are Linux kernel regressions tracked using a bot?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj~  hžhhŸh³h MrubhØ)”}”(hX\  Tracking regressions completely manually has proven to be quite hard due to the
distributed and loosely structured nature of Linux kernel development process.
That's why the Linux kernel's regression tracker developed regzbot to facilitate
the work, with the long term goal to automate regression tracking as much as
possible for everyone involved.”h]”hX`  Tracking regressions completely manually has proven to be quite hard due to the
distributed and loosely structured nature of Linux kernel development process.
Thatâ€™s why the Linux kernelâ€™s regression tracker developed regzbot to facilitate
the work, with the long term goal to automate regression tracking as much as
possible for everyone involved.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mthj~  hžhubhØ)”}”(hX?  Regzbot works by watching for replies to reports of tracked regressions.
Additionally, it's looking out for posted or committed patches referencing such
reports with "Link:" tags; replies to such patch postings are tracked as well.
Combined this data provides good insights into the current state of the fixing
process.”h]”hXE  Regzbot works by watching for replies to reports of tracked regressions.
Additionally, itâ€™s looking out for posted or committed patches referencing such
reports with â€œLink:â€ tags; replies to such patch postings are tracked as well.
Combined this data provides good insights into the current state of the fixing
process.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mzhj~  hžhubeh}”(h]”Œ<why-and-how-are-linux-kernel-regressions-tracked-using-a-bot”ah ]”h"]”Œ=why and how are linux kernel regressions tracked using a bot?”ah$]”h&]”uh1hÂhjF  hžhhŸh³h MrubhÃ)”}”(hhh]”(hÈ)”}”(hŒ6How to see which regressions regzbot tracks currently?”h]”hŒ6How to see which regressions regzbot tracks currently?”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj³  hžhhŸh³h MubhØ)”}”(hŒXCheck out `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.”h]”(hŒ
Check out ”…””}”(hjÄ  hžhhŸNh NubjF  )”}”(hŒM`regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_”h]”hŒregzbotâ€™s web-interface”…””}”(hjÌ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œregzbot's web-interface”jW  Œ0https://linux-regtracking.leemhuis.info/regzbot/”uh1jE  hjÄ  ubjZ  )”}”(hŒ3 <https://linux-regtracking.leemhuis.info/regzbot/>”h]”h}”(h]”Œid1”ah ]”h"]”h$]”Œregzbot's web-interface”ah&]”Œrefuri”jÜ  uh1jY  jh  KhjÄ  ubhŒ.”…””}”(hjÄ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mƒhj³  hžhubeh}”(h]”Œ5how-to-see-which-regressions-regzbot-tracks-currently”ah ]”h"]”Œ6how to see which regressions regzbot tracks currently?”ah$]”h&]”uh1hÂhjF  hžhhŸh³h MubhÃ)”}”(hhh]”(hÈ)”}”(hŒ:What kind of issues are supposed to be tracked by regzbot?”h]”hŒ:What kind of issues are supposed to be tracked by regzbot?”…””}”(hjÿ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjü  hžhhŸh³h M†ubhØ)”}”(hX%  The bot is meant to track regressions, hence please don't involve regzbot for
regular issues. But it's okay for the Linux kernel's regression tracker if you
involve regzbot to track severe issues, like reports about hangs, corrupted
data, or internal errors (Panic, Oops, BUG(), warning, ...).”h]”hX+  The bot is meant to track regressions, hence please donâ€™t involve regzbot for
regular issues. But itâ€™s okay for the Linux kernelâ€™s regression tracker if you
involve regzbot to track severe issues, like reports about hangs, corrupted
data, or internal errors (Panic, Oops, BUG(), warning, ...).”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mˆhjü  hžhubeh}”(h]”Œ9what-kind-of-issues-are-supposed-to-be-tracked-by-regzbot”ah ]”h"]”Œ:what kind of issues are supposed to be tracked by regzbot?”ah$]”h&]”uh1hÂhjF  hžhhŸh³h M†ubhÃ)”}”(hhh]”(hÈ)”}”(hŒ.How to change aspects of a tracked regression?”h]”hŒ.How to change aspects of a tracked regression?”…””}”(hj&	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj#	  hžhhŸh³h MŽubhØ)”}”(hX¡  By using a 'regzbot command' in a direct or indirect reply to the mail with the
report. The easiest way to do that: find the report in your "Sent" folder or the
mailing list archive and reply to it using your mailer's "Reply-all" function.
In that mail, use one of the following commands in a stand-alone paragraph (IOW:
use blank lines to separate one or multiple of these commands from the rest of
the mail's text).”h]”hX±  By using a â€˜regzbot commandâ€™ in a direct or indirect reply to the mail with the
report. The easiest way to do that: find the report in your â€œSentâ€ folder or the
mailing list archive and reply to it using your mailerâ€™s â€œReply-allâ€ function.
In that mail, use one of the following commands in a stand-alone paragraph (IOW:
use blank lines to separate one or multiple of these commands from the rest of
the mailâ€™s text).”…””}”(hj4	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mhj#	  hžhubjo  )”}”(hX@  * Update when the regression started to happen, for example after performing a
  bisection::

      #regzbot introduced: 1f2e3d4c5d

* Set or update the title::

      #regzbot title: foo

* Monitor a discussion or bugzilla.kernel.org ticket where additions aspects of
  the issue or a fix are discussed:::

      #regzbot monitor: https://lore.kernel.org/r/30th.anniversary.repost@klaava.Helsinki.FI/
      #regzbot monitor: https://bugzilla.kernel.org/show_bug.cgi?id=123456789

* Point to a place with further details of interest, like a mailing list post
  or a ticket in a bug tracker that are slightly related, but about a different
  topic::

      #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=123456789

* Mark a regression as invalid::

      #regzbot invalid: wasn't a regression, problem has always existed
”h]”ju  )”}”(hhh]”(j   )”}”(hŒ~Update when the regression started to happen, for example after performing a
bisection::

    #regzbot introduced: 1f2e3d4c5d
”h]”(hØ)”}”(hŒXUpdate when the regression started to happen, for example after performing a
bisection::”h]”hŒWUpdate when the regression started to happen, for example after performing a
bisection:”…””}”(hjM	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M—hjI	  ubj   )”}”(hŒ#regzbot introduced: 1f2e3d4c5d”h]”hŒ#regzbot introduced: 1f2e3d4c5d”…””}”hj[	  sbah}”(h]”h •,)      ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h MšhjI	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjF	  ubj   )”}”(hŒ3Set or update the title::

    #regzbot title: foo
”h]”(hØ)”}”(hŒSet or update the title::”h]”hŒSet or update the title:”…””}”(hjs	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Mœhjo	  ubj   )”}”(hŒ#regzbot title: foo”h]”hŒ#regzbot title: foo”…””}”hj	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h Mžhjo	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjF	  ubj   )”}”(hX  Monitor a discussion or bugzilla.kernel.org ticket where additions aspects of
the issue or a fix are discussed:::

    #regzbot monitor: https://lore.kernel.org/r/30th.anniversary.repost@klaava.Helsinki.FI/
    #regzbot monitor: https://bugzilla.kernel.org/show_bug.cgi?id=123456789
”h]”(hØ)”}”(hŒqMonitor a discussion or bugzilla.kernel.org ticket where additions aspects of
the issue or a fix are discussed:::”h]”hŒpMonitor a discussion or bugzilla.kernel.org ticket where additions aspects of
the issue or a fix are discussed::”…””}”(hj™	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M hj•	  ubj   )”}”(hŒŸ#regzbot monitor: https://lore.kernel.org/r/30th.anniversary.repost@klaava.Helsinki.FI/
#regzbot monitor: https://bugzilla.kernel.org/show_bug.cgi?id=123456789”h]”hŒŸ#regzbot monitor: https://lore.kernel.org/r/30th.anniversary.repost@klaava.Helsinki.FI/
#regzbot monitor: https://bugzilla.kernel.org/show_bug.cgi?id=123456789”…””}”hj§	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h M£hj•	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjF	  ubj   )”}”(hŒìPoint to a place with further details of interest, like a mailing list post
or a ticket in a bug tracker that are slightly related, but about a different
topic::

    #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=123456789
”h]”(hØ)”}”(hŒ¡Point to a place with further details of interest, like a mailing list post
or a ticket in a bug tracker that are slightly related, but about a different
topic::”h]”hŒ Point to a place with further details of interest, like a mailing list post
or a ticket in a bug tracker that are slightly related, but about a different
topic:”…””}”(hj¿	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¦hj»	  ubj   )”}”(hŒD#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=123456789”h]”hŒD#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=123456789”…””}”hjÍ	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h Mªhj»	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjF	  ubj   )”}”(hŒfMark a regression as invalid::

    #regzbot invalid: wasn't a regression, problem has always existed
”h]”(hØ)”}”(hŒMark a regression as invalid::”h]”hŒMark a regression as invalid:”…””}”(hjå	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M¬hjá	  ubj   )”}”(hŒA#regzbot invalid: wasn't a regression, problem has always existed”h]”hŒA#regzbot invalid: wasn't a regression, problem has always existed”…””}”hjó	  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jŸ  hŸh³h M®hjá	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j  hjF	  ubeh}”(h]”h ]”h"]”h$]”h&]”jd  je  uh1jt  hŸh³h M—hjB	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jn  hŸh³h M—hj#	  hžhubhØ)”}”(hX‹  Regzbot supports a few other commands primarily used by developers or people
tracking regressions. They and more details about the aforementioned regzbot
commands can be found in the `getting started guide
<https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md>`_ and
the `reference documentation <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md>`_
for regzbot.”h]”(hŒ·Regzbot supports a few other commands primarily used by developers or people
tracking regressions. They and more details about the aforementioned regzbot
commands can be found in the ”…””}”(hj
  hžhhŸNh NubjF  )”}”(hŒa`getting started guide
<https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md>`_”h]”hŒgetting started guide”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œgetting started guide”jW  ŒFhttps://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md”uh1jE  hj
  ubjZ  )”}”(hŒI
<https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md>”h]”h}”(h]”Œgetting-started-guide”ah ]”h"]”Œgetting started guide”ah$]”h&]”Œrefuri”j+
  uh1jY  jh  Khj
  ubhŒ	 and
the ”…””}”(hj
  hžhhŸNh NubjF  )”}”(hŒ]`reference documentation <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md>`_”h]”hŒreference documentation”…””}”(hj=
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”Œreference documentation”jW  Œ@https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md”uh1jE  hj
  ubjZ  )”}”(hŒC <https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md>”h]”h}”(h]”Œreference-documentation”ah ]”h"]”Œreference documentation”ah$]”h&]”Œrefuri”jM
  uh1jY  jh  Khj
  ubhŒ
for regzbot.”…””}”(hj
  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h M°hj#	  hžhubh¢)”}”(hŒend-of-content”h]”hŒend-of-content”…””}”hje
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hj#	  hžhhŸh³h M¸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 developers" for author attribution and link
this as source:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-regressions.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 developers" for author attribution and link
this as source:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/reporting-regressions.rst”…””}”hjs
  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1h¡hj#	  hžhhŸh³h M¾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j#	  hžhhŸh³h MÃubeh}”(h]”Œ-how-to-change-aspects-of-a-tracked-regression”ah ]”h"]”Œ.how to change aspects of a tracked regression?”ah$]”h&]”uh1hÂhjF  hžhhŸh³h MŽubeh}”(h]”Œ+more-about-regression-tracking-with-regzbot”ah ]”h"]”Œ-more about regression tracking with "regzbot"”ah$]”h&]”uh1hÂhjÈ  hžhhŸh³h Meubeh}”(h]”Œ>all-the-details-on-linux-kernel-regressions-relevant-for-users”ah ]”h"]”Œ>all the details on linux kernel regressions relevant for users”ah$]”h&]”uh1hÂhhÄhžhhŸh³h K&ubeh}”(h]”Œreporting-regressions”ah ]”h"]”Œreporting regressions”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Â  jd  ja  j¤
  j¡
  j  j
  jL  jI  jA  j>  jŸ  jœ  jÁ  j¾  jˆ  j…  j.  j+  jh  je  j  jŒ  j¶  j³  j  j  jC  j@  jg  jd  jT  jQ  jœ  j™  jÑ  jÎ  j  j  j-  j*  jT  jQ  j{  jx  j°  j­  jå  jâ  j  j	  jA  j>  j¦  j£  jw  jt  jÛ  jØ  j  j  j;  j8  jœ
  j™
  j{  jx  j°  j­  jù  jö  j 	  j	  j”
  j‘
  j5
  j2
  jW
  jT
  uŒ	nametypes”}”(j¬
  ‰jÅ  ‰jd  ˆj¤
  ‰j  ‰jL  ‰jA  ‰jŸ  ˆjÁ  ˆjˆ  ˆj.  ˆjh  ‰j  ‰j¶  ‰j  ‰jC  ‰jg  ‰jT  ˆjœ  ‰jÑ  ‰j  ‰j-  ‰jT  ‰j{  ‰j°  ‰jå  ‰j  ‰jA  ‰j¦  ‰jw  ˆjÛ  ‰j  ‰j;  ‰jœ
  ‰j{  ‰j°  ‰jù  ‰j 	  ‰j”
  ‰j5
  ˆjW
  ˆuh}”(j©
  hÄjÂ  j	  ja  j[  j¡
  jÈ  j
  jÙ  jI  jê  j>  jO  jœ  j–  j¾  j¸  j…  j  j+  j%  je  jD  jŒ  jk  j³  j’  j  j¹  j@  j  jd  j!  jQ  jK  j™  jj  jÎ  jŸ  j  jÔ  j*  j	  jQ  j0  jx  jW  j­  j~  jâ  j³  j	  jè  j>  j  j£  jD  jt  jn  jØ  j©  j  jÞ  j8  j  j™
  jF  jx  jW  j­  j~  jö  j³  jã  jÝ  j	  jü  j‘
  j#	  j2
  j,
  jT
  jN
  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”“”}”jà
  Ks…”R”Œparse_messages”]”hŒsystem_message”“”)”}”(hhh]”hØ)”}”(hŒ:Duplicate explicit target name: "regzbot's web-interface".”h]”hŒ@Duplicate explicit target name: â€œregzbotâ€™s web-interfaceâ€.”…””}”(hj9  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj6  ubah}”(h]”h ]”h"]”h$]”h&]”jã  aŒlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kuh1j4  hj³  hžhhŸh³h M„ubaŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.