€•Vn      Œ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”Œ1/translations/zh_CN/process/researcher-guidelines”Œ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”Œ1/translations/zh_TW/process/researcher-guidelines”Œ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”Œ1/translations/it_IT/process/researcher-guidelines”Œ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”Œ1/translations/ja_JP/process/researcher-guidelines”Œ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”Œ1/translations/ko_KR/process/researcher-guidelines”Œ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”Œ1/translations/sp_SP/process/researcher-guidelines”Œ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Œ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒK/var/lib/git/docbuild/linux/Documentation/process/researcher-guidelines.rst”h KubhŒtarget”“”)”}”(hŒ.. _researcher_guidelines:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œresearcher-guidelines”uh1h´h KhhhžhhŸh³ubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒResearcher Guidelines”h]”hŒResearcher Guidelines”…””}”(hhÉhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhhÄhžhhŸh³h KubhŒ	paragraph”“”)”}”(hX  The Linux kernel community welcomes transparent research on the Linux
kernel, the activities involved in producing it, and any other byproducts
of its development. Linux benefits greatly from this kind of research, and
most aspects of Linux are driven by research in one form or another.”h]”hX  The Linux kernel community welcomes transparent research on the Linux
kernel, the activities involved in producing it, and any other byproducts
of its development. Linux benefits greatly from this kind of research, and
most aspects of Linux are driven by research in one form or another.”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hXs  The community greatly appreciates if researchers can share preliminary
findings before making their results public, especially if such research
involves security. Getting involved early helps both improve the quality
of research and ability for Linux to improve from it. In any case,
sharing open access copies of the published research with the community
is recommended.”h]”hXs  The community greatly appreciates if researchers can share preliminary
findings before making their results public, especially if such research
involves security. Getting involved early helps both improve the quality
of research and ability for Linux to improve from it. In any case,
sharing open access copies of the published research with the community
is recommended.”…””}”(hhçhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hXw  This document seeks to clarify what the Linux kernel community considers
acceptable and non-acceptable practices when conducting such research. At
the very least, such research and related activities should follow
standard research ethics rules. For more background on research ethics
generally, ethics in technology, and research of developer communities
in particular, see:”h]”hXw  This document seeks to clarify what the Linux kernel community considers
acceptable and non-acceptable practices when conducting such research. At
the very least, such research and related activities should follow
standard research ethics rules. For more background on research ethics
generally, ethics in technology, and research of developer communities
in particular, see:”…””}”(hhõhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒT`History of Research Ethics <https://www.unlv.edu/research/ORI-HSR/history-ethics>`_”h]”hØ)”}”(hj  h]”(hŒ	reference”“”)”}”(hj  h]”hŒHistory of Research Ethics”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒHistory of Research Ethics”Œrefuri”Œ4https://www.unlv.edu/research/ORI-HSR/history-ethics”uh1j  hj  ubhµ)”}”(hŒ7 <https://www.unlv.edu/research/ORI-HSR/history-ethics>”h]”h}”(h]”Œhistory-of-research-ethics”ah ]”h"]”Œhistory of research ethics”ah$]”h&]”Œrefuri”j#  uh1h´Œ
referenced”Khj  ubeh}”(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Œ=`IEEE Ethics <https://www.ieee.org/about/ethics/index.html>`_”h]”hØ)”}”(hj@  h]”(j  )”}”(hj@  h]”hŒIEEE Ethics”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒIEEE Ethics”j"  Œ,https://www.ieee.org/about/ethics/index.html”uh1j  hjB  ubhµ)”}”(hŒ/ <https://www.ieee.org/about/ethics/index.html>”h]”h}”(h]”Œieee-ethics”ah ]”h"]”Œieee ethics”ah$]”h&]”Œrefuri”jT  uh1h´j1  KhjB  ubeh}”(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Œ~`Developer and Researcher Views on the Ethics of Experiments on Open-Source Projects <https://arxiv.org/pdf/2112.13217.pdf>`_
”h]”hØ)”}”(hŒ}`Developer and Researcher Views on the Ethics of Experiments on Open-Source Projects <https://arxiv.org/pdf/2112.13217.pdf>`_”h]”(j  )”}”(hjt  h]”hŒSDeveloper and Researcher Views on the Ethics of Experiments on Open-Source Projects”…””}”(hjv  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒSDeveloper and Researcher Views on the Ethics of Experiments on Open-Source Projects”j"  Œ$https://arxiv.org/pdf/2112.13217.pdf”uh1j  hjr  ubhµ)”}”(hŒ' <https://arxiv.org/pdf/2112.13217.pdf>”h]”h}”(h]”ŒSdeveloper-and-researcher-views-on-the-ethics-of-experiments-on-open-source-projects”ah ]”h"]”ŒSdeveloper and researcher views on the ethics of experiments on open-source projects”ah$]”h&]”Œrefuri”j…  uh1h´j1  Khjr  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Khjn  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j  hŸh³h KhhÄhžhubhØ)”}”(hXF  The Linux kernel community expects that everyone interacting with the
project is participating in good faith to make Linux better. Research on
any publicly-available artifact (including, but not limited to source
code) produced by the Linux kernel community is welcome, though research
on developers must be distinctly opt-in.”h]”hXF  The Linux kernel community expects that everyone interacting with the
project is participating in good faith to make Linux better. Research on
any publicly-available artifact (including, but not limited to source
code) produced by the Linux kernel community is welcome, though research
on developers must be distinctly opt-in.”…””}”(hj§  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KhhÄhžhubhØ)”}”(hŒðPassive research that is based entirely on publicly available sources,
including posts to public mailing lists and commits to public
repositories, is clearly permissible. Though, as with any research,
standard ethics must still be followed.”h]”hŒðPassive research that is based entirely on publicly available sources,
including posts to public mailing lists and commits to public
repositories, is clearly permissible. Though, as with any research,
standard ethics must still be followed.”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K%hhÄhžhubhØ)”}”(hX  Active research on developer behavior, however, must be done with the
explicit agreement of, and full disclosure to, the individual developers
involved. Developers cannot be interacted with/experimented on without
consent; this, too, is standard research ethics.”h]”hX  Active research on developer behavior, however, must be done with the
explicit agreement of, and full disclosure to, the individual developers
involved. Developers cannot be interacted with/experimented on without
consent; this, too, is standard research ethics.”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K*hhÄhžhubhÃ)”}”(hhh]”(hÈ)”}”(hŒSurveys”h]”hŒSurveys”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhjÑ  hžhhŸh³h K0ubhØ)”}”(hX  Research often takes the form of surveys sent to maintainers or
contributors.  As a general rule, though, the kernel community derives
little value from these surveys.  The kernel development process works
because every developer benefits from their participation, even working
with others who have different goals.  Responding to a survey, though, is a
one-way demand placed on busy developers with no corresponding benefit to
themselves or to the kernel community as a whole.  For this reason, this
method of research is discouraged.”h]”hX  Research often takes the form of surveys sent to maintainers or
contributors.  As a general rule, though, the kernel community derives
little value from these surveys.  The kernel development process works
because every developer benefits from their participation, even working
with others who have different goals.  Responding to a survey, though, is a
one-way demand placed on busy developers with no corresponding benefit to
themselves or to the kernel community as a whole.  For this reason, this
method of research is discouraged.”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K2hjÑ  hžhubhØ)”}”(hX  Kernel community members already receive far too much email and are likely
to perceive survey requests as just another demand on their time.  Sending
such requests deprives the community of valuable contributor time and is
unlikely to yield a statistically useful response.”h]”hX  Kernel community members already receive far too much email and are likely
to perceive survey requests as just another demand on their time.  Sending
such requests deprives the community of valuable contributor time and is
unlikely to yield a statistically useful response.”…””}”(hjð  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K;hjÑ  hžhubhØ)”}”(hXˆ  As an alternative, researchers should consider attending developer events,
hosting sessions where the research project and its benefits to the
participants can be explained, and interacting directly with the community
there.  The information received will be far richer than that obtained from
an email survey, and the community will gain from the ability to learn from
your insights as well.”h]”hXˆ  As an alternative, researchers should consider attending developer events,
hosting sessions where the research project and its benefits to the
participants can be explained, and interacting directly with the community
there.  The information received will be far richer than that obtained from
an email survey, and the community will gain from the ability to learn from
your insights as well.”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K@hjÑ  hžhubeh}”(h]”Œsurveys”ah ]”h"]”Œsurveys”ah$]”h&]”uh1hÂhhÄhžhhŸh³h K0ubhÃ)”}”(hhh]”(hÈ)”}”(hŒPatches”h]”hŒPatches”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÇhj  hžhhŸh³h KHubhØ)”}”(hXt  To help clarify: sending patches to developers *is* interacting
with them, but they have already consented to receiving *good faith
contributions*. Sending intentionally flawed/vulnerable patches or
contributing misleading information to discussions is not consented
to. Such communication can be damaging to the developer (e.g. draining
time, effort, and morale) and damaging to the project by eroding
the entire developer community's trust in the contributor (and the
contributor's organization as a whole), undermining efforts to provide
constructive feedback to contributors, and putting end users at risk of
software flaws.”h]”(hŒ/To help clarify: sending patches to developers ”…””}”(hj%  hžhhŸNh NubhŒemphasis”“”)”}”(hŒ*is*”h]”hŒis”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j-  hj%  ubhŒE interacting
with them, but they have already consented to receiving ”…””}”(hj%  hžhhŸNh Nubj.  )”}”(hŒ*good faith
contributions*”h]”hŒgood faith
contributions”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j-  hj%  ubhXæ  . Sending intentionally flawed/vulnerable patches or
contributing misleading information to discussions is not consented
to. Such communication can be damaging to the developer (e.g. draining
time, effort, and morale) and damaging to the project by eroding
the entire developer communityâ€™s trust in the contributor (and the
contributorâ€™s organization as a whole), undermining efforts to provide
constructive feedback to contributors, and putting end users at risk of
software flaws.”…””}”(hj%  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KJhj  hžhubhØ)”}”(hŒýParticipation in the development of Linux itself by researchers, as
with anyone, is welcomed and encouraged. Research into Linux code is
a common practice, especially when it comes to developing or running
analysis tools that produce actionable results.”h]”hŒýParticipation in the development of Linux itself by researchers, as
with anyone, is welcomed and encouraged. Research into Linux code is
a common practice, especially when it comes to developing or running
analysis tools that produce actionable results.”…””}”(hjY  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KUhj  hžhubhØ)”}”(hX  When engaging with the developer community, sending a patch has
traditionally been the best way to make an impact. Linux already has
plenty of known bugs -- what's much more helpful is having vetted fixes.
Before contributing, carefully read the appropriate documentation:”h]”hX  When engaging with the developer community, sending a patch has
traditionally been the best way to make an impact. Linux already has
plenty of known bugs -- whatâ€™s much more helpful is having vetted fixes.
Before contributing, carefully read the appropriate documentation:”…””}”(hjg  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KZhj  hžhubj  )”}”(hhh]”(j	  )”}”(hŒ-Documentation/process/development-process.rst”h]”hØ)”}”(hjz  h]”hŒ-Documentation/process/development-process.rst”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K_hjx  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hju  hžhhŸh³h Nubj	  )”}”(hŒ,Documentation/process/submitting-patches.rst”h]”hØ)”}”(hj‘  h]”hŒ,Documentation/process/submitting-patches.rst”…””}”(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ju  hžhhŸh³h Nubj	  )”}”(hŒ.Documentation/admin-guide/reporting-issues.rst”h]”hØ)”}”(hj¨  h]”hŒ.Documentation/admin-guide/reporting-issues.rst”…””}”(hjª  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kahj¦  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hju  hžhhŸh³h Nubj	  )”}”(hŒ(Documentation/process/security-bugs.rst
”h]”hØ)”}”(hŒ'Documentation/process/security-bugs.rst”h]”hŒ'Documentation/process/security-bugs.rst”…””}”(hjÁ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kbhj½  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hju  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j¥  j¦  uh1j  hŸh³h K_hj  hžhubhØ)”}”(hŒThen send a patch (including a commit log with all the details listed
below) and follow up on any feedback from other developers.”h]”hŒThen send a patch (including a commit log with all the details listed
below) and follow up on any feedback from other developers.”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kdhj  hžhubhØ)”}”(hŒÃWhen sending patches produced from research, the commit logs should
contain at least the following details, so that developers have
appropriate context for understanding the contribution. Answer:”h]”hŒÃWhen sending patches produced from research, the commit logs should
contain at least the following details, so that developers have
appropriate context for understanding the contribution. Answer:”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kghj  hžhubj  )”}”(hhh]”(j	  )”}”(hŒ1What is the specific problem that has been found?”h]”hØ)”}”(hjü  h]”hŒ1What is the specific problem that has been found?”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kkhjú  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ5How could the problem be reached on a running system?”h]”hØ)”}”(hj  h]”hŒ5How could the problem be reached on a running system?”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Klhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ>What effect would encountering the problem have on the system?”h]”hØ)”}”(hj*  h]”hŒ>What effect would encountering the problem have on the system?”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kmhj(  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ¨How was the problem found? Specifically include details about any
testing, static or dynamic analysis programs, and any other tools or
methods used to perform the work.”h]”hØ)”}”(hŒ¨How was the problem found? Specifically include details about any
testing, static or dynamic analysis programs, and any other tools or
methods used to perform the work.”h]”hŒ¨How was the problem found? Specifically include details about any
testing, static or dynamic analysis programs, and any other tools or
methods used to perform the work.”…””}”(hjC  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Knhj?  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ©Which version of Linux was the problem found on? Using the most recent
release or a recent linux-next branch is strongly preferred (see
Documentation/process/howto.rst).”h]”hØ)”}”(hŒ©Which version of Linux was the problem found on? Using the most recent
release or a recent linux-next branch is strongly preferred (see
Documentation/process/howto.rst).”h]”hŒ©Which version of Linux was the problem found on? Using the most recent
release or a recent linux-next branch is strongly preferred (see
Documentation/process/howto.rst).”…””}”(hj[  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h KqhjW  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒJWhat was changed to fix the problem, and why it is believed to be correct?”h]”hØ)”}”(hjq  h]”hŒJWhat was changed to fix the problem, and why it is believed to be correct?”…””}”(hjs  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kthjo  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ4How was the change build tested and run-time tested?”h]”hØ)”}”(hjˆ  h]”hŒ4How was the change build tested and run-time tested?”…””}”(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j÷  hžhhŸh³h Nubj	  )”}”(hŒhWhat prior commit does this change fix? This should go in a "Fixes:"
tag as the documentation describes.”h]”hØ)”}”(hŒhWhat prior commit does this change fix? This should go in a "Fixes:"
tag as the documentation describes.”h]”hŒlWhat prior commit does this change fix? This should go in a â€œFixes:â€
tag as the documentation describes.”…””}”(hj¡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kvhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubj	  )”}”(hŒ`Who else has reviewed this patch? This should go in appropriate
"Reviewed-by:" tags; see below.
”h]”hØ)”}”(hŒ_Who else has reviewed this patch? This should go in appropriate
"Reviewed-by:" tags; see below.”h]”hŒcWho else has reviewed this patch? This should go in appropriate
â€œReviewed-by:â€ tags; see below.”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kxhjµ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hj÷  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”j¥  j¦  uh1j  hŸh³h Kkhj  hžhubhØ)”}”(hŒFor example::”h]”hŒFor example:”…””}”(hjÓ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K{hj  hžhubhŒliteral_block”“”)”}”(hXÈ  From: Author <author@email>
Subject: [PATCH] drivers/foo_bar: Add missing kfree()

The error path in foo_bar driver does not correctly free the allocated
struct foo_bar_info. This can happen if the attached foo_bar device
rejects the initialization packets sent during foo_bar_probe(). This
would result in a 64 byte slab memory leak once per device attach,
wasting memory resources over time.

This flaw was found using an experimental static analysis tool we are
developing, LeakMagic[1], which reported the following warning when
analyzing the v5.15 kernel release:

 path/to/foo_bar.c:187: missing kfree() call?

Add the missing kfree() to the error path. No other references to
this memory exist outside the probe function, so this is the only
place it can be freed.

x86_64 and arm64 defconfig builds with CONFIG_FOO_BAR=y using GCC
11.2 show no new warnings, and LeakMagic no longer warns about this
code path. As we don't have a FooBar device to test with, no runtime
testing was able to be performed.

[1] https://url/to/leakmagic/details

Reported-by: Researcher <researcher@email>
Fixes: aaaabbbbccccdddd ("Introduce support for FooBar")
Signed-off-by: Author <author@email>
Reviewed-by: Reviewer <reviewer@email>”h]”hXÈ  From: Author <author@email>
Subject: [PATCH] drivers/foo_bar: Add missing kfree()

The error path in foo_bar driver does not correctly free the allocated
struct foo_bar_info. This can happen if the attached foo_bar device
rejects the initialization packets sent during foo_bar_probe(). This
would result in a 64 byte slab memory leak once per device attach,
wasting memory resources over time.

This flaw was found using an experimental static analysis tool we are
developing, LeakMagic[1], which reported the following warning when
analyzing the v5.15 kernel release:

 path/to/foo_bar.c:187: missing kfree() call?

Add the missing kfree() to the error path. No other references to
this memory exist outside the probe function, so this is the only
place it can be freed.

x86_64 and arm64 defconfig builds with CONFIG_FOO_BAR=y using GCC
11.2 show no new warnings, and LeakMagic no longer warns about this
code path. As we don't have a FooBar device to test with, no runtime
testing was able to be performed.

[1] https://url/to/leakmagic/details

Reported-by: Researcher <researcher@email>
Fixes: aaaabbbbccccdddd ("Introduce support for FooBar")
Signed-off-by: Author <author@email>
Reviewed-by: Reviewer <reviewer@email>”…””}”hjã  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1já  hŸh³h K}hj  hžhubhØ)”}”(hX~  If you are a first time contributor it is recommended that the patch
itself be vetted by others privately before being posted to public lists.
(This is required if you have been explicitly told your patches need
more careful internal review.) These people are expected to have their
"Reviewed-by" tag included in the resulting patch. Finding another
developer familiar with Linux contribution, especially within your own
organization, and having them help with reviews before sending them to
the public mailing lists tends to significantly improve the quality of the
resulting patches, and there by reduces the burden on other developers.”h]”hX‚  If you are a first time contributor it is recommended that the patch
itself be vetted by others privately before being posted to public lists.
(This is required if you have been explicitly told your patches need
more careful internal review.) These people are expected to have their
â€œReviewed-byâ€ tag included in the resulting patch. Finding another
developer familiar with Linux contribution, especially within your own
organization, and having them help with reviews before sending them to
the public mailing lists tends to significantly improve the quality of the
resulting patches, and there by reduces the burden on other developers.”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h Kœhj  hžhubhØ)”}”(hX4  If no one can be found to internally review patches and you need
help finding such a person, or if you have any other questions
related to this document and the developer community's expectations,
please reach out to the private Technical Advisory Board mailing list:
<tech-board@groups.linuxfoundation.org>.”h]”(hX  If no one can be found to internally review patches and you need
help finding such a person, or if you have any other questions
related to this document and the developer communityâ€™s expectations,
please reach out to the private Technical Advisory Board mailing list:
<”…””}”(hjÿ  hžhhŸNh Nubj  )”}”(hŒ%tech-board@groups.linuxfoundation.org”h]”hŒ%tech-board@groups.linuxfoundation.org”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œ,mailto:tech-board@groups.linuxfoundation.org”uh1j  hjÿ  ubhŒ>.”…””}”(hjÿ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh³h K¦hj  hžhubeh}”(h]”Œpatches”ah ]”h"]”Œpatches”ah$]”h&]”uh1hÂhhÄhžhhŸh³h KHubeh}”(h]”(hÁŒid1”eh ]”h"]”(Œresearcher guidelines”Œresearcher_guidelines”eh$]”h&]”uh1hÂhhhžhhŸh³h KŒexpect_referenced_by_name”}”j/  h¶sŒexpect_referenced_by_id”}”hÁh¶subeh}”(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”jY  Œ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”}”hÁ]”h¶asŒnameids”}”(j/  hÁj.  j+  j-  j*  j^  j[  j  jŒ  j  j  j&  j#  uŒ	nametypes”}”(j/  ˆj.  ‰j-  ˆj^  ˆj  ˆj  ‰j&  ‰uh}”(hÁhÄj+  hÄj*  j$  j[  jU  jŒ  j†  j  jÑ  j#  j  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”“”}”jg  Ks…”R”Œparse_messages”]”Œtransform_messages”]”hŒsystem_message”“”)”}”(hhh]”hØ)”}”(hhh]”hŒ;Hyperlink target "researcher-guidelines" is not referenced.”…””}”hjÃ  sbah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjÀ  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h³Œline”Kuh1j¾  ubaŒtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.