netdev - Re: [PATCH] Phonet: sockets list through proc

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: <1248091650.4549.107.camel@violet>
Date:	Mon, 20 Jul 2009 14:07:30 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	David Miller <davem@...emloft.net>
Cc:	remi.denis-courmont@...ia.com, netdev@...r.kernel.org
Subject: Re: [PATCH] Phonet: sockets list through proc_fs

Hi Dave,

> > On Monday 20 July 2009 13:21:01 ext Marcel Holtmann wrote:
> >> > It's just like most network protocols exposing their sockets list in
> >> > /proc/net. Debugging/monitoring indeed.
> >>
> >> I think that for new protocols, we should not do this anymore and just
> >> use debugfs. Since that is exactly its job.
> > 
> > Requiring debugfs for something like 'netstat' sounds restrictive to me...
> 
> Me too.

hold on, what has netstat to do with Phonet support? Does netstat now
support Phonet or what are we trying to achieve here?

And if we are talking about debugging information, then they should go
into debugfs and not /proc. At least for new protocols.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html