From: Vadim Kochan <vadim4j@gmail.com>
To: roopa <roopa@cumulusnetworks.com>
Cc: David Ahern <dsa@cumulusnetworks.com>,
stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] ip route get: change exit to return to support batch commands
Date: Fri, 16 Oct 2015 09:08:34 +0300 [thread overview]
Message-ID: <20151016060834.GA13468@angus-think.lan> (raw)
In-Reply-To: <56206B53.1080709@cumulusnetworks.com>
On Thu, Oct 15, 2015 at 08:13:23PM -0700, roopa wrote:
> On 10/15/15, 7:38 PM, David Ahern wrote:
> > Hi Roopa:
> >
> > On 10/15/15 4:23 PM, Roopa Prabhu wrote:
> >> From: Roopa Prabhu <roopa@cumulusnetworks.com>
> >>
> >> replace exit with return -2 on rtnl_talk failure
> >>
> >> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> >> ---
> >> ip/iproute.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/ip/iproute.c b/ip/iproute.c
> >> index da25548..b137f55 100644
> >> --- a/ip/iproute.c
> >> +++ b/ip/iproute.c
> >> @@ -1643,7 +1643,7 @@ static int iproute_get(int argc, char **argv)
> >> req.r.rtm_family = AF_INET;
> >>
> >> if (rtnl_talk(&rth, &req.n, &req.n, sizeof(req)) < 0)
> >> - exit(2);
> >> + return -2;
> >>
> >> if (connected && !from_ok) {
> >> struct rtmsg *r = NLMSG_DATA(&req.n);
> >>
> >
> > Why return -2 vs exit(2)? What does the change mean to a user or the functionality of ip?
> Stephen has documented this someplace. I have seen it before. I now forget where. Right now i am just following
> the rest of the code.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
IMHO I think it would be good to have #define's for these return values.
prev parent reply other threads:[~2015-10-16 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 22:23 [PATCH iproute2] ip route get: change exit to return to support batch commands Roopa Prabhu
2015-10-16 2:38 ` David Ahern
2015-10-16 3:13 ` roopa
2015-10-16 6:08 ` Vadim Kochan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151016060834.GA13468@angus-think.lan \
--to=vadim4j@gmail.com \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).