linux-kernel - [PATCH 3/4] mark loop functions as noinline_for

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <480E0A7C.2060907@redhat.com>
Date:	Tue, 22 Apr 2008 10:55:40 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	linux-kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 3/4] mark loop functions as noinline_for_stack

Use the self-documenting noinline_for_stack attribute
in loop functions.

Signed-off-by: Eric Sandeen <sandeen@...hat.com>
---

Index: linux-2.6.25/drivers/block/loop.c
===================================================================
--- linux-2.6.25.orig/drivers/block/loop.c	2008-04-22 10:31:05.015471118 -0500
+++ linux-2.6.25/drivers/block/loop.c	2008-04-22 10:51:18.070407735 -0500
@@ -1182,9 +1182,8 @@ struct compat_loop_info {
 
 /*
  * Transfer 32-bit compatibility structure in userspace to 64-bit loop info
- * - noinlined to reduce stack space usage in main part of driver
  */
-static noinline int
+static noinline_for_stack int
 loop_info64_from_compat(const struct compat_loop_info __user *arg,
 			struct loop_info64 *info64)
 {
@@ -1215,9 +1214,8 @@ loop_info64_from_compat(const struct com
 
 /*
  * Transfer 64-bit loop info to 32-bit compatibility structure in userspace
- * - noinlined to reduce stack space usage in main part of driver
  */
-static noinline int
+static noinline_for_stack int
 loop_info64_to_compat(const struct loop_info64 *info64,
 		      struct compat_loop_info __user *arg)
 {

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/