Hi,
I have three (five) questions regarding IPX code in 2.3.13. I do not know,
which parts are addressed in upcoming networking patch, but just in case
that they are not...
(1) Should not IPX spinlock around walking through ipx_interfaces
and so on? For example, where ipxitf_find_using_phys (running from
ipx_rcv) locks against removing interface in ipxitf_down (synchronize_bh()
before kfree_s(intrfc,...) should be enough).
(2) IPX does not provide SIOCGIFCONF ioctl. I was using specific IPX code
to implement SIOCGIFCONF on IPX sockets. Last week, when I found
register_gifconf function, I rewrote it to use this function (so IPX
interfaces are returned on any socket type SIOCGIFCONF). Should not be one
of these ways included in kernel? And what's better? I did not find any
problems with returning IPX interfaces through SIOCGIFCONF on IPX socket
(ifconfig still works correctly), but maybe it is explicitly disallowed in
some RFC/POSIX? Currently, DECnet and IPV4 register their gifconf handlers,
econet and appletalk calls standard dev_ioctl() for SIOCGIFCONF, but do
not register their interfaces (this brings question: What does IPV6?)
(3) IPX's connect() now only says to kernel that send() should pick
this address as other endpoint - it does not affect recv/recvfrom. Should
not connect() also limit recv/recvfrom to receive data from connected
endpoint only (currently I have patch which allows you to create multiple
listeners on socket 12345 as long as each socket is connected to
different endpoint (+ one socket can be unconnected to receive all
packets from unknown endpoints).
[(4) I also still maintain special patch, which sets source address
of outgoing IPX frames to address of interface through which it is going
to wire instead of address you bind socket to - but because of it can
be worked around by MSG_DONTROUTE & multiple sockets... (current kernel
has it hardwired for ports 0x452 & 0x453) ]
[(5) Is there someone who could profit from MSG_DONTROUTE implementation
for af_ipx? In oposite from four points above I have not written it yet.]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
