diff options
author | Bernard Pidoux F6BVP | 2009-12-17 06:25:18 +0100 |
---|---|---|
committer | David S. Miller | 2010-01-04 06:21:16 +0100 |
commit | 1f731b63752dac76ff4dbf568a08ff2e3663316f (patch) | |
tree | 452db46db4863269d7368afcafdf2f071c803c11 /drivers/scsi/osst.c | |
parent | via-velocity: Give RX descriptors to the NIC later on open or MTU change (diff) | |
download | kernel-qcow2-linux-1f731b63752dac76ff4dbf568a08ff2e3663316f.tar.gz kernel-qcow2-linux-1f731b63752dac76ff4dbf568a08ff2e3663316f.tar.xz kernel-qcow2-linux-1f731b63752dac76ff4dbf568a08ff2e3663316f.zip |
rose_loopback_timer sets VC number <= ROSE_DEFAULT_MAXVC
cat /proc/net/rose displayed a rose sockets abnormal lci value, i.e.
greater than maximum number of VCs per neighbour allowed.
This number prevents further test of lci value during rose operations.
Example (lines shortened) :
[bernard]# cat /proc/net/rose
dest_addr dest_call src_addr src_call dev lci neigh st vs vr va
* * 2080175520 F6BVP-1 rose0 000 00000 0 0 0 0
2080175520 FPAD-0 2080175520 WP-0 rose0 FFE 00001 3 0 0 0
Here are the default parameters :
linux/include/net/rose.h:#define ROSE_DEFAULT_MAXVC 50 /* Maximum number of VCs per neighbour */
linux/net/rose/af_rose.c:int sysctl_rose_maximum_vcs = ROSE_DEFAULT_MAXVC;
With the following patch, rose_loopback_timer() attributes a VC number
within limits.
Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/scsi/osst.c')
0 files changed, 0 insertions, 0 deletions