Re: xfrm_user reliability

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Oct 07, 2003 at 02:06:24PM +0400, kuznet@ms2.inr.ac.ru wrote:
> 
> Error is returned in any case, it is ENOBUFS returned by recvmsg()
> when we cannot return error specific for given request.

That's all I need.

The only problem now is that various NETLINK implementations do not
always generate the overrun.  For example, if the netlink_ack() in
xfrm_user.c fails to allocate memory nothing is returned.

I suppose the simplest solution is to get netlink_ack() to call
netlink_overrun()?

> I think, memory bounds are better to keep really hard.

Agreed.

Thanks,
-- 
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email:  Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux