Hi,
Now I've added multiple range support to BALANCE too. It's a simple port
of the multiple range support in SAME.
I had the same problem here with one variable in my struct containing the
value of a previously used struct. it's mr->ipnum in balance_check that's
misbehaving according to me. Well I reset it to 0 and everything seems to
be working fine now.
I don't know if anyone's ever asked for support for multiple ranges in
BALANCE but since it was an easy port from SAME (they are _very_ alike)
I thought that I'd let the Core-team descide if this is something that's
needed.
/Martin
--
Linux hackers are funny people: They count the time in patchlevels.
Now I've added multiple range support to BALANCE too. It's a simple port
of the multiple range support in SAME.
I had the same problem here with one variable in my struct containing the
value of a previously used struct. it's mr->ipnum in balance_check that's
misbehaving according to me. Well I reset it to 0 and everything seems to
be working fine now.
I don't know if anyone's ever asked for support for multiple ranges in
BALANCE but since it was an easy port from SAME (they are _very_ alike)
I thought that I'd let the Core-team descide if this is something that's
needed.
/Martin
--
Linux hackers are funny people: They count the time in patchlevels.
Attached Files:
-
patch-o-matic.patch (7.53 KB)
-
userspace.patch (4.69 KB)