How are Linux kernel bugs being tracked?

Clash Royale CLAN TAG#URR8PPP
What an hour of Googling bring out that mainstream Linux kernel bugs are being logged in two distinct systems:
Mailing list
This is the Linux kernel development discussion and bug reporting
mailing list.
The mailing list is archived by a number of services, e.g.
- Gmane
- lkml
- MARC
- Mail archive
- Indiana
Bugzilla
This is the Kernel Tracker system (based on Bugzilla) for posting bugs
against the mainline Linux kernels (not distribution kernels).
Distributions, e.g. Ubuntu have their own bug tracker which may be set to track upstream bugs.
I wonder that,
- Are the bugs reported on the either of the services synced back to the other?
- Assuming that the mailing list and the bugzilla are not mirrors of each other (i.e. those are independent and bugs are not synced), how do Linux developers coordinate between the bugs reported across services?
- Isn't it inconvenient to refer to the bugs reported to mailing list later on due to not having any bug ID? (I understand that one can refer by a mailing archive URL, however doesn't look professional IMO)
- Should a new bug be reported to any one of the services or both?
linux-kernel bugs bugzilla
add a comment |
What an hour of Googling bring out that mainstream Linux kernel bugs are being logged in two distinct systems:
Mailing list
This is the Linux kernel development discussion and bug reporting
mailing list.
The mailing list is archived by a number of services, e.g.
- Gmane
- lkml
- MARC
- Mail archive
- Indiana
Bugzilla
This is the Kernel Tracker system (based on Bugzilla) for posting bugs
against the mainline Linux kernels (not distribution kernels).
Distributions, e.g. Ubuntu have their own bug tracker which may be set to track upstream bugs.
I wonder that,
- Are the bugs reported on the either of the services synced back to the other?
- Assuming that the mailing list and the bugzilla are not mirrors of each other (i.e. those are independent and bugs are not synced), how do Linux developers coordinate between the bugs reported across services?
- Isn't it inconvenient to refer to the bugs reported to mailing list later on due to not having any bug ID? (I understand that one can refer by a mailing archive URL, however doesn't look professional IMO)
- Should a new bug be reported to any one of the services or both?
linux-kernel bugs bugzilla
add a comment |
What an hour of Googling bring out that mainstream Linux kernel bugs are being logged in two distinct systems:
Mailing list
This is the Linux kernel development discussion and bug reporting
mailing list.
The mailing list is archived by a number of services, e.g.
- Gmane
- lkml
- MARC
- Mail archive
- Indiana
Bugzilla
This is the Kernel Tracker system (based on Bugzilla) for posting bugs
against the mainline Linux kernels (not distribution kernels).
Distributions, e.g. Ubuntu have their own bug tracker which may be set to track upstream bugs.
I wonder that,
- Are the bugs reported on the either of the services synced back to the other?
- Assuming that the mailing list and the bugzilla are not mirrors of each other (i.e. those are independent and bugs are not synced), how do Linux developers coordinate between the bugs reported across services?
- Isn't it inconvenient to refer to the bugs reported to mailing list later on due to not having any bug ID? (I understand that one can refer by a mailing archive URL, however doesn't look professional IMO)
- Should a new bug be reported to any one of the services or both?
linux-kernel bugs bugzilla
What an hour of Googling bring out that mainstream Linux kernel bugs are being logged in two distinct systems:
Mailing list
This is the Linux kernel development discussion and bug reporting
mailing list.
The mailing list is archived by a number of services, e.g.
- Gmane
- lkml
- MARC
- Mail archive
- Indiana
Bugzilla
This is the Kernel Tracker system (based on Bugzilla) for posting bugs
against the mainline Linux kernels (not distribution kernels).
Distributions, e.g. Ubuntu have their own bug tracker which may be set to track upstream bugs.
I wonder that,
- Are the bugs reported on the either of the services synced back to the other?
- Assuming that the mailing list and the bugzilla are not mirrors of each other (i.e. those are independent and bugs are not synced), how do Linux developers coordinate between the bugs reported across services?
- Isn't it inconvenient to refer to the bugs reported to mailing list later on due to not having any bug ID? (I understand that one can refer by a mailing archive URL, however doesn't look professional IMO)
- Should a new bug be reported to any one of the services or both?
linux-kernel bugs bugzilla
linux-kernel bugs bugzilla
edited Jun 30 '16 at 6:12
Holmes.Sherlock
asked Jun 30 '16 at 5:48
Holmes.SherlockHolmes.Sherlock
224110
224110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is really a very very partial answer, but at least in the netdev mailing list (for the networking subsystem), there are sometimes messages about bugs reported in bugzilla; these messages are sent to the netdev mailing list, with cc to potential owners of the code, for example:
http://www.spinics.net/lists/netdev/msg351687.html
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f293025%2fhow-are-linux-kernel-bugs-being-tracked%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is really a very very partial answer, but at least in the netdev mailing list (for the networking subsystem), there are sometimes messages about bugs reported in bugzilla; these messages are sent to the netdev mailing list, with cc to potential owners of the code, for example:
http://www.spinics.net/lists/netdev/msg351687.html
add a comment |
This is really a very very partial answer, but at least in the netdev mailing list (for the networking subsystem), there are sometimes messages about bugs reported in bugzilla; these messages are sent to the netdev mailing list, with cc to potential owners of the code, for example:
http://www.spinics.net/lists/netdev/msg351687.html
add a comment |
This is really a very very partial answer, but at least in the netdev mailing list (for the networking subsystem), there are sometimes messages about bugs reported in bugzilla; these messages are sent to the netdev mailing list, with cc to potential owners of the code, for example:
http://www.spinics.net/lists/netdev/msg351687.html
This is really a very very partial answer, but at least in the netdev mailing list (for the networking subsystem), there are sometimes messages about bugs reported in bugzilla; these messages are sent to the netdev mailing list, with cc to potential owners of the code, for example:
http://www.spinics.net/lists/netdev/msg351687.html
edited Sep 2 '16 at 15:35
Jeff Schaller
41.5k1056132
41.5k1056132
answered Sep 2 '16 at 14:42
Rami RosenRami Rosen
1602
1602
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f293025%2fhow-are-linux-kernel-bugs-being-tracked%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown