Re: [PATCH net-next v3] genetlink: do not parse attributes for families with zero maxattr

2019-10-13 Thread David Miller
From: Michal Kubecek Date: Fri, 11 Oct 2019 09:40:09 +0200 > Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing > to a separate function") moved attribute buffer allocation and attribute > parsing from genl_family_rcv_msg_doit() into a separate function >

Re: [PATCH net-next v3] genetlink: do not parse attributes for families with zero maxattr

2019-10-12 Thread Jakub Kicinski
On Fri, 11 Oct 2019 09:40:09 +0200, Michal Kubecek wrote: > Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing > to a separate function") moved attribute buffer allocation and attribute > parsing from genl_family_rcv_msg_doit() into a separate function >

Re: [PATCH net-next v3] genetlink: do not parse attributes for families with zero maxattr

2019-10-11 Thread Jiri Pirko
Fri, Oct 11, 2019 at 09:40:09AM CEST, mkube...@suse.cz wrote: >Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing >to a separate function") moved attribute buffer allocation and attribute >parsing from genl_family_rcv_msg_doit() into a separate function

[PATCH net-next v3] genetlink: do not parse attributes for families with zero maxattr

2019-10-11 Thread Michal Kubecek
Commit c10e6cf85e7d ("net: genetlink: push attrbuf allocation and parsing to a separate function") moved attribute buffer allocation and attribute parsing from genl_family_rcv_msg_doit() into a separate function genl_family_rcv_msg_attrs_parse() which, unlike the previous code, calls