Blame view
Documentation/stable_kernel_rules.txt
2.53 KB
fc185d95e [PATCH] Add the r... |
1 |
Everything you ever wanted to know about Linux 2.6 -stable releases. |
e48e99093 [PATCH] Docs upda... |
2 3 |
Rules on what kind of patches are accepted, and which ones are not, into the "-stable" tree: |
fc185d95e [PATCH] Add the r... |
4 5 |
- It must be obviously correct and tested. |
84eb8d060 Fix "can not" in ... |
6 |
- It cannot be bigger than 100 lines, with context. |
fc185d95e [PATCH] Add the r... |
7 8 |
- It must fix only one thing. - It must fix a real bug that bothers people (not a, "This could be a |
e48e99093 [PATCH] Docs upda... |
9 |
problem..." type thing). |
fc185d95e [PATCH] Add the r... |
10 11 |
- It must fix a problem that causes a build error (but not for things marked CONFIG_BROKEN), an oops, a hang, data corruption, a real |
e48e99093 [PATCH] Docs upda... |
12 13 14 15 |
security issue, or some "oh, that's not good" issue. In short, something critical. - No "theoretical race condition" issues, unless an explanation of how the race can be exploited is also provided. |
84eb8d060 Fix "can not" in ... |
16 |
- It cannot contain any "trivial" fixes in it (spelling changes, |
e48e99093 [PATCH] Docs upda... |
17 |
whitespace cleanups, etc). |
fc185d95e [PATCH] Add the r... |
18 |
- It must be accepted by the relevant subsystem maintainer. |
e48e99093 [PATCH] Docs upda... |
19 |
- It must follow the Documentation/SubmittingPatches rules. |
fc185d95e [PATCH] Add the r... |
20 21 22 23 24 25 |
Procedure for submitting patches to the -stable tree: - Send the patch, after verifying that it follows the above rules, to stable@kernel.org. |
e48e99093 [PATCH] Docs upda... |
26 27 28 29 30 |
- The sender will receive an ACK when the patch has been accepted into the queue, or a NAK if the patch is rejected. This response might take a few days, according to the developer's schedules. - If accepted, the patch will be added to the -stable queue, for review by other developers. |
fc185d95e [PATCH] Add the r... |
31 |
- Security patches should not be sent to this alias, but instead to the |
e48e99093 [PATCH] Docs upda... |
32 |
documented security@kernel.org address. |
fc185d95e [PATCH] Add the r... |
33 34 35 |
Review cycle: |
e48e99093 [PATCH] Docs upda... |
36 37 38 39 40 |
- When the -stable maintainers decide for a review cycle, the patches will be sent to the review committee, and the maintainer of the affected area of the patch (unless the submitter is the maintainer of the area) and CC: to the linux-kernel mailing list. - The review committee has 48 hours in which to ACK or NAK the patch. |
fc185d95e [PATCH] Add the r... |
41 |
- If the patch is rejected by a member of the committee, or linux-kernel |
e48e99093 [PATCH] Docs upda... |
42 43 44 45 46 47 |
members object to the patch, bringing up issues that the maintainers and members did not realize, the patch will be dropped from the queue. - At the end of the review cycle, the ACKed patches will be added to the latest -stable release, and a new -stable release will happen. - Security patches will be accepted into the -stable tree directly from the security kernel team, and not go through the normal review cycle. |
fc185d95e [PATCH] Add the r... |
48 |
Contact the kernel security team for more details on this procedure. |
5d3f083d8 Fix typos in /Doc... |
49 |
Review committee: |
fc185d95e [PATCH] Add the r... |
50 |
|
e48e99093 [PATCH] Docs upda... |
51 52 |
- This is made up of a number of kernel developers who have volunteered for this task, and a few that haven't. |