On Tue, Jan 29, 2008 at 10:10:30AM +0100, Jarek Poplawski wrote: > On Tue, Jan 29, 2008 at 09:49:15AM +0100, Jarek Poplawski wrote: > > On Tue, Jan 29, 2008 at 02:30:47AM +0200, Julian Anastasov wrote: > ... > > > fa_match is some existing alias that matches all new parameters. > > > As NLM_F_REPLACE changes the first alternative route for > > > tos+priority if fa_match == fa_first (we are replacing alias that > > > matches all parameters) we return 0, only that routing cache is not > > > flushed - nothing is replaced/changed. So, "fa == fa_match" means > > > "replace will not change existing parameters", return 0 as this is > > > not an error. > > > > Probably I miss something, but what parameters do we change if > > (fa_match) && (fa != fa_match)? Isn't this "goto out" in any case? > > OOPS! You mean change is needed, but we can't do this! (I'm so slow...)
...On the other hand, I wonder how bad would be switching these two to avoid this error? After all "replace" with this "add or change" meaning looks quite permissive, and after all it was used before with no such errors, so, even if correct, it could still break some scripts... Jarek P. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
