linux-kernel - [1/1] Export __lock_page

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-next>] [day] [month] [year] [list]

Message-ID: <20080514141157.GA27047@2ka.mipt.ru>
Date:	Wed, 14 May 2008 18:11:58 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [1/1] Export __lock_page_killable()

Hi.

There are users, who would like to use lock_page_killable() in modules,
so far there are no users in kernel, but for consistency it can be
exported without them.

Not that it is particulary needed, but copying page_waitqueue() in
modules is frowned upon and unlikely to be exported either.

As a side note, do we want interruptible and time limited locking for
those who knows what is being done?

Signed-off-by: Evgeniy Polyakov <johnpol@....mipt.ru>

diff --git a/mm/filemap.c b/mm/filemap.c
index 07e9d92..0a4fea5 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -610,6 +610,7 @@ int __lock_page_killable(struct page *page)
 	return __wait_on_bit_lock(page_waitqueue(page), &wait,
 					sync_page_killable, TASK_KILLABLE);
 }
+EXPORT_SYMBOL(__lock_page_killable);
 
 /**
  * __lock_page_nosync - get a lock on the page, without calling sync_page()


-- 
	Evgeniy Polyakov
--
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/