linux-kernel - [PATCH 2/2] init, mount: export the name_to_dev

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]

Date:	Tue, 25 May 2010 10:46:51 -0500
From:	Will Drewry <wad@...omium.org>
To:	linux-kernel@...r.kernel.org
Cc:	Al Viro <viro@...iv.linux.org.uk>, Nick Piggin <npiggin@...e.de>,
	Tejun Heo <tj@...nel.org>,
	Scott James Remnant <scott@...ntu.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Harald Hoyer <harald@...hat.com>,
	Christoph Lameter <cl@...ux-foundation.org>, agk@...hat.com,
	snitzer@...hat.com, Will Drewry <wad@...omium.org>
Subject: [PATCH 2/2] init, mount: export the name_to_dev_t symbol

This change only adds EXPORT_SYMBOL() for name_to_dev_t.

name_to_dev_t is in use outside of init/ but is not 'officially'
exported.  It provides behavior that is useful for any code that may be
need to lookup a block device by major:minor or registered kernel name,
especially before there is a root filesystem.

Hopefully, this is the appropriate use of EXPORT_SYMBOL().  This
specific function seems to be a stable interface and is available
in include/linux/mount.h.

Signed-off-by: Will Drewry <wad@...omium.org>
---
 init/do_mounts.c      |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/init/do_mounts.c b/init/do_mounts.c
index a322b13..b9206e7 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -144,6 +144,7 @@ fail:
 done:
 	return res;
 }
+EXPORT_SYMBOL(name_to_dev_t);
 
 static int __init root_dev_setup(char *line)
 {
-- 
1.7.0.4

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