netdev - Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation

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, 17 Jun 2008 01:14:59 +0530
From:	"Amar Mudrankit" <amar.mudrankit@...gic.com>
To:	"Patrick McHardy" <kaber@...sh.net>
Cc:	netdev@...r.kernel.org, rdreier@...co.com,
	general@...ts.openfabrics.org, poornima.kamath@...gic.com
Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation

>> I was looking at latest release of iproute2, in which I could not
>> locate fill_xstats. Can you help me to locate this?
>
> ->fill_xstats is in the kernel, in iproute its ->print_xstats.

I was looking at kernel code net/8021q/vlan_netlink.c on which I have
following queries:

a.  Is it a correct file in kernel I m referring to?
b.  vlan_fill_info is a function to send parameters back to user
level. What is the role of skb as an argument to function? Is some
network operation expected?
c.  How exactly the kernel API ops->get_size comes into play? I guess
user prog should first get the size of parameters that will be
returned by driver before calling ops->fill_info.
d.  Can somebody briefly introduce struct nlattr? It looks like all
parameters flow through this structure.

Thanks and Regards,
Amar S Mudrankit
--
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