linux-kernel - Re: [PATCH] Move rlb table dump to procfs

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20141017.164838.1035248404947187957.davem@davemloft.net>
Date:	Fri, 17 Oct 2014 16:48:38 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	emunson@...mai.com
Cc:	netdev@...r.kernel.org, andy@...yhouse.net, vfalico@...il.com,
	j.vosburgh@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Move rlb table dump to procfs

From: Eric B Munson <emunson@...mai.com>
Date: Fri, 17 Oct 2014 14:41:52 -0400

> Because debugfs is not net namespace aware, it is currently not
> possible to dump the RLB hash table when network namespaces are enabled.
> This patch creates a second proc file called IFNAME_rlb_table for
> bonding interfaces that use adaptive load balancing which will expose
> this table to userspace.  It also removes all the debugfs code from the
> bonding module as the RLB hash was the only entry in debugfs.
> 
> Signed-off-by: Eric B Munson <emunson@...mai.com>

It's meant to be a debugging facility, which has no stable API
and is not something the user can depend upon it.

Once you move it to procfs, it's basically over and we are
stuck with this forever.

I think the intention of this meaning to be a debug facility for
developers is very clear.

I'm not applying this, sorry.
--
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/