From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 2/2] nvme-rdma: Add handling for connecting to IPv6 targets
Date: Thu, 18 Aug 2016 10:44:49 +0300 [thread overview]
Message-ID: <2b4f4727-58b5-c62e-e5fd-cc5e5b4ae6be@grimberg.me> (raw)
In-Reply-To: <CAG4TOxPNnUKWeh7FUY8YB127sx8yMu41FuP4hxUMCan_HWQmVQ@mail.gmail.com>
> I think adding a new helper that parses both v4 and v6 addresses +
> scope ID seems like the best thing for now. I did a grep for in6_pton
> and it looks like at least fs/cifs/netmisc.c and net/sunrpc/addr.c
> could use the helper.
>
> What do you think of adding inet_pton_with_scope() to
> net/core/utils.c? I'm open to better ideas on the name. But I can
> code that up and use it in nvme, as well as convert over the two
> places I mentioned above. The first parameter of the function can be
> an af, and the caller can pass in AF_UNSPEC, AF_INET, or AF_INET6 to
> restrict the parsing to one type of address (or not).
Hey Roland,
Are you looking into this?
I'd love to get it into 4.9...
next prev parent reply other threads:[~2016-08-18 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-31 7:27 [PATCH 1/2] nvme-rdma: Don't leak uninitialized memory in connect request private data Roland Dreier
2016-07-31 7:27 ` [PATCH 2/2] nvme-rdma: Add handling for connecting to IPv6 targets Roland Dreier
2016-07-31 8:45 ` Sagi Grimberg
2016-07-31 10:58 ` Sagi Grimberg
2016-07-31 15:33 ` Roland Dreier
2016-08-01 5:58 ` Sagi Grimberg
2016-08-01 6:15 ` Sagi Grimberg
2016-08-01 11:09 ` Christoph Hellwig
2016-08-01 11:24 ` Sagi Grimberg
2016-08-01 15:50 ` Christoph Hellwig
2016-08-01 16:06 ` Roland Dreier
2016-08-02 6:43 ` Sagi Grimberg
2016-08-02 12:51 ` Christoph Hellwig
2016-08-18 7:44 ` Sagi Grimberg [this message]
2016-08-22 4:44 ` Roland Dreier
2016-08-22 6:47 ` Sagi Grimberg
2016-08-02 6:41 ` Sagi Grimberg
2016-08-01 11:09 ` Christoph Hellwig
2016-07-31 8:44 ` [PATCH 1/2] nvme-rdma: Don't leak uninitialized memory in connect request private data Sagi Grimberg
2016-08-01 11:07 ` Christoph Hellwig
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=2b4f4727-58b5-c62e-e5fd-cc5e5b4ae6be@grimberg.me \
--to=sagi@grimberg.me \
/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).