From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EF3E94E61E for ; Thu, 7 Dec 2023 20:25:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="DvF7TWnb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 19E33C433C7; Thu, 7 Dec 2023 20:25:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1701980759; bh=r6pNC5v7QT5EdXzchmdJJF2GJJSUXK92g5ieduPietg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=DvF7TWnboRelWsdXnyEGz9NOCjYeNibagMjtM92jygcoq/k9i+DSyzK3jMYLs4cgU PsafU7SE84XUI6qw6vySUqGUwANXIxtkot8rUzd3rJXr39PxYHAwThL6OEeeQ7lilF 3RPOBL4HV5FQT4qIvaSXgdezJ0kpR5IIyEOAIxZ2brRqPieJZnVXbFH2Ebc6z9RClB WnLfELScPwJ9LYES29MfthFrhTW8D6iFSky/TZblBI1NBC1x9OaSpUaOo03jbjPHBd DSR+2MuGPi2L/ER4Th1nC2vi8jNSe90UbXybQOXWnrW8PqeXtxAlFco31uIZsA8rv6 uPVcPm4NPcBbg== Message-ID: Date: Thu, 7 Dec 2023 13:25:58 -0700 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net-next] ipv6: do not check fib6_has_expires() in fib6_info_release() Content-Language: en-US To: Eric Dumazet , "David S . Miller" , Jakub Kicinski , Paolo Abeni Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com, syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com, Kui-Feng Lee References: <20231207201322.549000-1-edumazet@google.com> From: David Ahern In-Reply-To: <20231207201322.549000-1-edumazet@google.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 12/7/23 1:13 PM, Eric Dumazet wrote: > My prior patch went a bit too far, because apparently fib6_has_expires() > could be true while f6i->gc_link is not hashed yet. yes, and I got distracted by that stack trace and avoiding errors in the create function. The diff I sent does not solve any corruption with list since the newly allocated f6i is not linked (and gc-link is initialized). Kui-Feng: no need to send that patch again since it is not really changing anything. Let's see if the other warn on triggers. > > fib6_set_expires_locked() can indeed set RTF_EXPIRES > while f6i->fib6_table is NULL. > > Original syzbot reports were about corruptions caused > by dangling f6i->gc_link. > > Fixes: 5a08d0065a91 ("ipv6: add debug checks in fib6_info_release()") > Reported-by: syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com > Signed-off-by: Eric Dumazet > Cc: David Ahern > Cc: Kui-Feng Lee > --- > include/net/ip6_fib.h | 1 - > 1 file changed, 1 deletion(-) > Reviewed-by: David Ahern