Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1673455
| From | Matthias Schiffer <mschiffer@universe-factory.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration |
| Date | 2017-06-23 12:20 +0200 |
| Message-ID | <tVtQZ-Rn-9@gated-at.bofh.it> (permalink) |
| References | <tTZUZ-8vX-3@gated-at.bofh.it> <tTZUZ-8vX-11@gated-at.bofh.it> <tVsBA-8nM-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 06/23/2017 10:52 AM, Jiri Benc wrote: > This patchset looks good overall (would send my Acked-by for most of > this but I'm late). > > On Mon, 19 Jun 2017 10:03:55 +0200, Matthias Schiffer wrote: >> Log messages in these >> functions are removed, as it is generally unexpected to find error output >> for netlink requests in the kernel log. Userspace should be able to handle >> errors based on the error codes returned via netlink just fine. > > However, this is not really true. It's impossible to find out what went > wrong when you use e.g. iproute2 to configure a vxlan link. > > We really need to convert the kernel log messages to the extended > netlink errors. Since you removed them prematurely, could you please > work on that? > > Thanks, > > Jiri > I was told the extended netlink error facilities were not ready yet, has that changed since the last release? Off the top of my head, I can't think of any other setting I can do with iproute2 that will write its errors in the kernel log; but there are quite a lot settings that will just return a very unspecific error code. Isn't it more common for the userspace tool to handle diagnostics in such cases? Anyways, I will gladly work on improving the error handling if someone can give me a pointer how these extended netlink errors are used. Matthias
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration Jiri Benc <jbenc@redhat.com> - 2017-06-23 11:00 +0200
Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration Matthias Schiffer <mschiffer@universe-factory.net> - 2017-06-23 12:20 +0200
Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration Johannes Berg <johannes@sipsolutions.net> - 2017-06-23 12:30 +0200
Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration Matthias Schiffer <mschiffer@universe-factory.net> - 2017-06-23 14:10 +0200
Re: [PATCH net-next v3 1/6] vxlan: refactor verification and application of configuration Johannes Berg <johannes@sipsolutions.net> - 2017-06-23 15:40 +0200
csiph-web