From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754150AbdJIL65 (ORCPT ); Mon, 9 Oct 2017 07:58:57 -0400 Received: from s3.sipsolutions.net ([144.76.63.242]:38740 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751550AbdJIL6z (ORCPT ); Mon, 9 Oct 2017 07:58:55 -0400 Message-ID: <1507550326.26041.39.camel@sipsolutions.net> Subject: Re: [PATCH] netlink: do not set cb_running if dump's start() errs From: Johannes Berg To: "Jason A. Donenfeld" , davem@davemloft.net, Netdev , linux-kernel@vger.kernel.org Date: Mon, 09 Oct 2017 13:58:46 +0200 In-Reply-To: <20171009115648.25989-1-Jason@zx2c4.com> References: <20171009115648.25989-1-Jason@zx2c4.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.0-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2017-10-09 at 13:56 +0200, Jason A. Donenfeld wrote: > @@ -2266,16 +2266,17 @@ int __netlink_dump_start(struct sock *ssk, > struct sk_buff *skb, > cb->min_dump_alloc = control->min_dump_alloc; > cb->skb = skb; > > + if (cb->start) { > + ret = cb->start(cb); > + if (ret) > + goto error_unlock; > + } > + > nlk->cb_running = true; > > mutex_unlock(nlk->cb_mutex); Hmm. Now start is invoked with the mutex held, I'm not sure it actually _matters_, but that should probably be reviewed and mentioned in the commit log? johannes