Al Viro wrote:
On Wed, Jan 16, 2008 at 07:23:40AM -0700, Jonathan Corbet wrote:
Hi, Pavel,
[Adding Ulrich]
I use the last bit in the clone_flags for CLONE_LONGARG. When set it
will denote that the child_tidptr is not a pointer to a tid storage,
but the pointer to the struct
Save namespace context on the fib rule at the rule creation time and call
routing lookup in the correct namespace.
Signed-off-by: Denis V. Lunev [EMAIL PROTECTED]
Acked-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/net/fib_rules.h |1 +
net/core/fib_rules.c|2 ++
commit c064c4811b3e87ff8202f5a966ff4eea0bc54575
Author: Daniel Lezcano [EMAIL PROTECTED]
Date: Thu Jan 10 02:56:03 2008 -0800
[NETNS][IPV6]: Make ip6_frags per namespace.
The ip6_frags is moved to the network namespace structure. Because
there can be multiple instances
FIB rule-action should operate in the same namespace as fib_lookup.
This is definitely missed right now.
There are two ways to implement this: pass struct net into another rules
API call (2 levels) or place netns into rule struct directly. The second
approach seems better as the code will grow
The backward link from FIB rules operations to the network namespace will
allow to simplify the API a bit.
Signed-off-by: Denis V. Lunev [EMAIL PROTECTED]
Acked-by: Daniel Lezcano [EMAIL PROTECTED]
---
include/net/fib_rules.h |1 +
net/decnet/dn_rules.c |1 +
net/ipv4/fib_rules.c|
Remove struct net from fib_rules_register(unregister)/notify_change paths
and diet code size a bit.
add/remove: 0/0 grow/shrink: 10/12 up/down: 35/-100 (-65)
function old new delta
notify_rule_change 273 280 +7
Alexey Dobriyan wrote:
commit c064c4811b3e87ff8202f5a966ff4eea0bc54575
Author: Daniel Lezcano [EMAIL PROTECTED]
Date: Thu Jan 10 02:56:03 2008 -0800
[NETNS][IPV6]: Make ip6_frags per namespace.
The ip6_frags is moved to the network namespace structure. Because
there can be
Denis V. Lunev wrote:
FIB rule-action should operate in the same namespace as fib_lookup.
This is definitely missed right now.
There are two ways to implement this: pass struct net into another rules
API call (2 levels) or place netns into rule struct directly. The second
approach seems better
On Thu, Jan 17, 2008 at 11:40:42AM +0100, Daniel Lezcano wrote:
Alexey Dobriyan wrote:
commit c064c4811b3e87ff8202f5a966ff4eea0bc54575
Author: Daniel Lezcano [EMAIL PROTECTED]
Date: Thu Jan 10 02:56:03 2008 -0800
[NETNS][IPV6]: Make ip6_frags per namespace.
The ip6_frags is
Alexey Dobriyan wrote:
On Thu, Jan 17, 2008 at 11:40:42AM +0100, Daniel Lezcano wrote:
Alexey Dobriyan wrote:
commit c064c4811b3e87ff8202f5a966ff4eea0bc54575
Author: Daniel Lezcano [EMAIL PROTECTED]
Date: Thu Jan 10 02:56:03 2008 -0800
[NETNS][IPV6]: Make ip6_frags per namespace.
Have you tried using /etc/vz/conf/$VEID.start script? There are also
.stop, .mount and .umount. I'm sorry if it is not documented; will fix that.
Note that mount/umount scripts are both per-VE and global (global one is
called vps.mount/vps.umount), while start/stop are only per-VE. This can
I'm not very familiar with this syntaxes but I think it can be done
similarly :
snprintf(buf, sizeof(buf), VPS_CONF_DIR %d.%s, veid,
START_PREFIX);
if (stat_file(buf)) {
if (vps_exec_script(h, veid, res-fs.root, NULL, NULL,
buf, NULL, 0))
{
Jonathan Corbet wrote:
Heh, indeed. But we do seem to have a recurring problem of people
wanting to extend sys_foo() beyond the confines of its original API.
I've observed a few ways of doing that:
- create sys_foo2() (or sys_foo64(), or sys_fooat(), or sys_pfoo(),
or...) and add the new
13 matches
Mail list logo
