-1

Documentation/admin-guide/index.rst

reviewed

··· 36 36 37 37 reporting-issues 38 38 reporting-regressions 39 39 - security-bugs 40 39 bug-hunting 41 40 bug-bisect 42 41 tainted-kernels

+2 -2

Documentation/admin-guide/reporting-issues.rst

reviewed

··· 395 395 list of tracked regressions, to ensure it won't fall through the cracks. 396 396 397 397 What qualifies as security issue is left to your judgment. Consider reading 398 398 - Documentation/admin-guide/security-bugs.rst before proceeding, as it 398 398 + Documentation/process/security-bugs.rst before proceeding, as it 399 399 provides additional details how to best handle security issues. 400 400 401 401 An issue is a 'really severe problem' when something totally unacceptably bad ··· 1269 1269 the report's text to these addresses; but on top of it put a small note where 1270 1270 you mention that you filed it with a link to the ticket. 1271 1271 1272 1272 - See Documentation/admin-guide/security-bugs.rst for more information. 1272 1272 + See Documentation/process/security-bugs.rst for more information. 1273 1273 1274 1274 1275 1275 Duties after the report went out

Documentation/admin-guide/security-bugs.rst Documentation/process/security-bugs.rst

reviewed

+1 -1

Documentation/process/howto.rst

reviewed

··· 138 138 philosophy and is very important for people moving to Linux from 139 139 development on other Operating Systems. 140 140 141 141 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 141 141 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 142 142 If you feel you have found a security problem in the Linux kernel, 143 143 please follow the steps in this document to help notify the kernel 144 144 developers, and help solve the issue.

+8 -1

Documentation/process/index.rst

reviewed

··· 35 35 kernel-enforcement-statement 36 36 kernel-driver-statement 37 37 38 38 + For security issues, see: 39 39 + 40 40 + .. toctree:: 41 41 + :maxdepth: 1 42 42 + 43 43 + security-bugs 44 44 + embargoed-hardware-issues 45 45 + 38 46 Other guides to the community that are of interest to most developers are: 39 47 40 48 .. toctree:: ··· 55 47 submit-checklist 56 48 kernel-docs 57 49 deprecated 58 58 - embargoed-hardware-issues 59 50 maintainers 60 51 researcher-guidelines 61 52

+1 -1

Documentation/process/researcher-guidelines.rst

reviewed

··· 68 68 * Documentation/process/development-process.rst 69 69 * Documentation/process/submitting-patches.rst 70 70 * Documentation/admin-guide/reporting-issues.rst 71 71 - * Documentation/admin-guide/security-bugs.rst 71 71 + * Documentation/process/security-bugs.rst 72 72 73 73 Then send a patch (including a commit log with all the details listed 74 74 below) and follow up on any feedback from other developers.

+1 -1

Documentation/process/stable-kernel-rules.rst

reviewed

··· 39 39 40 40 Security patches should not be handled (solely) by the -stable review 41 41 process but should follow the procedures in 42 42 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>`. 42 42 + :ref:`Documentation/process/security-bugs.rst <securitybugs>`. 43 43 44 44 For all other submissions, choose one of the following procedures 45 45 -----------------------------------------------------------------

+1 -1

Documentation/process/submitting-patches.rst

reviewed

··· 254 254 to security@kernel.org. For severe bugs, a short embargo may be considered 255 255 to allow distributors to get the patch out to users; in such cases, 256 256 obviously, the patch should not be sent to any public lists. See also 257 257 - Documentation/admin-guide/security-bugs.rst. 257 257 + Documentation/process/security-bugs.rst. 258 258 259 259 Patches that fix a severe bug in a released kernel should be directed 260 260 toward the stable maintainers by putting a line like this::

+1 -1

Documentation/translations/it_IT/admin-guide/security-bugs.rst

reviewed

··· 1 1 .. include:: ../disclaimer-ita.rst 2 2 3 3 - :Original: :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 3 3 + :Original: :ref:`Documentation/process/security-bugs.rst <securitybugs>` 4 4 5 5 .. _it_securitybugs: 6 6

+1 -1

Documentation/translations/it_IT/process/submitting-patches.rst

reviewed

··· 272 272 distribuzioni di prendere la patch e renderla disponibile ai loro utenti; 273 273 in questo caso, ovviamente, la patch non dovrebbe essere inviata su alcuna 274 274 lista di discussione pubblica. Leggete anche 275 275 - Documentation/admin-guide/security-bugs.rst. 275 275 + Documentation/process/security-bugs.rst. 276 276 277 277 Patch che correggono bachi importanti su un kernel già rilasciato, dovrebbero 278 278 essere inviate ai manutentori dei kernel stabili aggiungendo la seguente riga::

+1 -1

Documentation/translations/ja_JP/howto.rst

reviewed

··· 167 167 このドキュメントは Linux 開発の思想を理解するのに非常に重要です。 168 168 そして、他のOSでの開発者が Linux に移る時にとても重要です。 169 169 170 170 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 170 170 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 171 171 もし Linux カーネルでセキュリティ問題を発見したように思ったら、こ 172 172 のドキュメントのステップに従ってカーネル開発者に連絡し、問題解決を 173 173 支援してください。

+1 -1

Documentation/translations/ko_KR/howto.rst

reviewed

··· 157 157 리눅스로 전향하는 사람들에게는 매우 중요하다. 158 158 159 159 160 160 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 160 160 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 161 161 여러분들이 리눅스 커널의 보안 문제를 발견했다고 생각한다면 이 문서에 162 162 나온 단계에 따라서 커널 개발자들에게 알리고 그 문제를 해결할 수 있도록 163 163 도와 달라.

+1 -1

Documentation/translations/sp_SP/howto.rst

reviewed

··· 135 135 de Linux y es muy importante para las personas que se mudan a Linux 136 136 tras desarrollar otros sistemas operativos. 137 137 138 138 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 138 138 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 139 139 Si cree que ha encontrado un problema de seguridad en el kernel de 140 140 Linux, siga los pasos de este documento para ayudar a notificar a los 141 141 desarrolladores del kernel y ayudar a resolver el problema.

+1 -1

Documentation/translations/sp_SP/process/submitting-patches.rst

reviewed

··· 276 276 poco de discreción y permitir que los distribuidores entreguen el parche a 277 277 los usuarios; en esos casos, obviamente, el parche no debe enviarse a 278 278 ninguna lista pública. Revise también 279 279 - Documentation/admin-guide/security-bugs.rst. 279 279 + Documentation/process/security-bugs.rst. 280 280 281 281 Los parches que corrigen un error grave en un kernel en uso deben dirigirse 282 282 hacia los maintainers estables poniendo una línea como esta::

+1 -1

Documentation/translations/zh_CN/admin-guide/security-bugs.rst

reviewed

··· 1 1 .. include:: ../disclaimer-zh_CN.rst 2 2 3 3 - :Original: :doc:`../../../admin-guide/security-bugs` 3 3 + :Original: :doc:`../../../process/security-bugs` 4 4 5 5 :译者: 6 6

+1 -1

Documentation/translations/zh_CN/process/howto.rst

reviewed

··· 125 125 这篇文档对于理解Linux的开发哲学至关重要。对于将开发平台从其他操作系 126 126 统转移到Linux的人来说也很重要。 127 127 128 128 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 128 128 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 129 129 如果你认为自己发现了Linux内核的安全性问题，请根据这篇文档中的步骤来 130 130 提醒其他内核开发者并帮助解决这个问题。 131 131

+1 -1

Documentation/translations/zh_TW/admin-guide/security-bugs.rst

reviewed

··· 2 2 3 3 .. include:: ../disclaimer-zh_TW.rst 4 4 5 5 - :Original: :doc:`../../../admin-guide/security-bugs` 5 5 + :Original: :doc:`../../../process/security-bugs` 6 6 7 7 :譯者: 8 8

+1 -1

Documentation/translations/zh_TW/process/howto.rst

reviewed

··· 128 128 這篇文檔對於理解Linux的開發哲學至關重要。對於將開發平台從其他操作系 129 129 統轉移到Linux的人來說也很重要。 130 130 131 131 - :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` 131 131 + :ref:`Documentation/process/security-bugs.rst <securitybugs>` 132 132 如果你認爲自己發現了Linux內核的安全性問題，請根據這篇文檔中的步驟來 133 133 提醒其他內核開發者並幫助解決這個問題。 134 134

+2 -2

MAINTAINERS

reviewed

··· 73 73 and ideally, should come with a patch proposal. Please do not send 74 74 automated reports to this list either. Such bugs will be handled 75 75 better and faster in the usual public places. See 76 76 - Documentation/admin-guide/security-bugs.rst for details. 76 76 + Documentation/process/security-bugs.rst for details. 77 77 78 78 8. Happy hacking. 79 79 ··· 18799 18799 SECURITY CONTACT 18800 18800 M: Security Officers <security@kernel.org> 18801 18801 S: Supported 18802 18802 - F: Documentation/admin-guide/security-bugs.rst 18802 18802 + F: Documentation/process/security-bugs.rst 18803 18803 18804 18804 SECURITY SUBSYSTEM 18805 18805 M: Paul Moore <paul@paul-moore.com>

+11 -5

drivers/base/cacheinfo.c

reviewed

··· 474 474 475 475 populate_leaves: 476 476 /* 477 477 - * populate_cache_leaves() may completely setup the cache leaves and 478 478 - * shared_cpu_map or it may leave it partially setup. 477 477 + * If LLC is valid the cache leaves were already populated so just go to 478 478 + * update the cpu map. 479 479 */ 480 480 - ret = populate_cache_leaves(cpu); 481 481 - if (ret) 482 482 - goto free_ci; 480 480 + if (!last_level_cache_is_valid(cpu)) { 481 481 + /* 482 482 + * populate_cache_leaves() may completely setup the cache leaves and 483 483 + * shared_cpu_map or it may leave it partially setup. 484 484 + */ 485 485 + ret = populate_cache_leaves(cpu); 486 486 + if (ret) 487 487 + goto free_ci; 488 488 + } 483 489 484 490 /* 485 491 * For systems using DT for cache hierarchy, fw_token

+13 -1

drivers/mtd/spi-nor/core.c

reviewed

··· 3343 3343 .remove = spi_nor_remove, 3344 3344 .shutdown = spi_nor_shutdown, 3345 3345 }; 3346 3346 - module_spi_mem_driver(spi_nor_driver); 3346 3346 + 3347 3347 + static int __init spi_nor_module_init(void) 3348 3348 + { 3349 3349 + return spi_mem_driver_register(&spi_nor_driver); 3350 3350 + } 3351 3351 + module_init(spi_nor_module_init); 3352 3352 + 3353 3353 + static void __exit spi_nor_module_exit(void) 3354 3354 + { 3355 3355 + spi_mem_driver_unregister(&spi_nor_driver); 3356 3356 + spi_nor_debugfs_shutdown(); 3357 3357 + } 3358 3358 + module_exit(spi_nor_module_exit); 3347 3359 3348 3360 MODULE_LICENSE("GPL v2"); 3349 3361 MODULE_AUTHOR("Huang Shijie <shijie8@gmail.com>");

+2

drivers/mtd/spi-nor/core.h

reviewed

··· 711 711 712 712 #ifdef CONFIG_DEBUG_FS 713 713 void spi_nor_debugfs_register(struct spi_nor *nor); 714 714 + void spi_nor_debugfs_shutdown(void); 714 715 #else 715 716 static inline void spi_nor_debugfs_register(struct spi_nor *nor) {} 717 717 + static inline void spi_nor_debugfs_shutdown(void) {} 716 718 #endif 717 719 718 720 #endif /* __LINUX_MTD_SPI_NOR_INTERNAL_H */

+8 -3

drivers/mtd/spi-nor/debugfs.c

reviewed

··· 226 226 nor->debugfs_root = NULL; 227 227 } 228 228 229 229 + static struct dentry *rootdir; 230 230 + 229 231 void spi_nor_debugfs_register(struct spi_nor *nor) 230 232 { 231 231 - struct dentry *rootdir, *d; 233 233 + struct dentry *d; 232 234 int ret; 233 235 234 234 - /* Create rootdir once. Will never be deleted again. */ 235 235 - rootdir = debugfs_lookup(SPI_NOR_DEBUGFS_ROOT, NULL); 236 236 if (!rootdir) 237 237 rootdir = debugfs_create_dir(SPI_NOR_DEBUGFS_ROOT, NULL); 238 238 ··· 246 246 debugfs_create_file("params", 0444, d, nor, &spi_nor_params_fops); 247 247 debugfs_create_file("capabilities", 0444, d, nor, 248 248 &spi_nor_capabilities_fops); 249 249 + } 250 250 + 251 251 + void spi_nor_debugfs_shutdown(void) 252 252 + { 253 253 + debugfs_remove(rootdir); 249 254 }