Details
-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Fix Version/s: OpenVZ-legacy
-
Component/s: Containers::Kernel
-
Security Level: Public
-
Environment:Operating System: Debian
Platform: x86_64 (AMD64)
-
External issue URL:
-
External issue ID:387
Description
Hi,
new kernel 2.6.18-028test007.1-smp on x86_64 (amd64):
Test: (in a VE:) Add some iptables rules and then clean all rules occures:
### iptables -F
### -> error :iptables: Memory allocation problem
### -> /proc/user_beancounters, numiptent is increased
# straced (relevant) infos:
22959 munmap(0x2b56efee6000, 4096) = 0
22959 socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
22959 getsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\337u\"\200\377\377\377\377\300\202`7\0\201\377"..., [84]) = 0
22959 getsockopt(3, SOL_IP, 0x41 /* IP_??? */, "filter\0\377\0\0\0\0\0\0\0\0\0\321P\0\0\0\0\0\377\377\377"..., [-4990645860720180424]) = 0
22959 setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 728) = -1 ENOMEM (Cannot allocate memory)
22959 write(2, "iptables: Memory allocation prob"..., 36) = 36
22959 exit_group(0x1, 0x3c, 0x1, 0, 0xe7 <unfinished ...>
### Test on x86 flushing iptables is running without problems ...
Regards,
Thorsten
new kernel 2.6.18-028test007.1-smp on x86_64 (amd64):
Test: (in a VE:) Add some iptables rules and then clean all rules occures:
### iptables -F
### -> error :iptables: Memory allocation problem
### -> /proc/user_beancounters, numiptent is increased
# straced (relevant) infos:
22959 munmap(0x2b56efee6000, 4096) = 0
22959 socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
22959 getsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\337u\"\200\377\377\377\377\300\202`7\0\201\377"..., [84]) = 0
22959 getsockopt(3, SOL_IP, 0x41 /* IP_??? */, "filter\0\377\0\0\0\0\0\0\0\0\0\321P\0\0\0\0\0\377\377\377"..., [-4990645860720180424]) = 0
22959 setsockopt(3, SOL_IP, 0x40 /* IP_??? */, "filter\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 728) = -1 ENOMEM (Cannot allocate memory)
22959 write(2, "iptables: Memory allocation prob"..., 36) = 36
22959 exit_group(0x1, 0x3c, 0x1, 0, 0xe7 <unfinished ...>
### Test on x86 flushing iptables is running without problems ...
Regards,
Thorsten