From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6D901C433F5 for ; Tue, 28 Aug 2018 15:59:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D4ED42087A for ; Tue, 28 Aug 2018 15:59:44 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D4ED42087A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ZenIV.linux.org.uk Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727395AbeH1TwC (ORCPT ); Tue, 28 Aug 2018 15:52:02 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:58656 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727112AbeH1TwB (ORCPT ); Tue, 28 Aug 2018 15:52:01 -0400 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.87 #1 (Red Hat Linux)) id 1fugP4-0002jR-RF; Tue, 28 Aug 2018 15:59:38 +0000 Date: Tue, 28 Aug 2018 16:59:38 +0100 From: Al Viro To: Cong Wang Cc: Jamal Hadi Salim , Kees Cook , LKML , Jiri Pirko , David Miller , Linux Kernel Network Developers Subject: Re: [PATCH] net: sched: Fix memory exposure from short TCA_U32_SEL Message-ID: <20180828155938.GF6515@ZenIV.linux.org.uk> References: <20180826055801.GA42063@beast> <20180826061534.GT6515@ZenIV.linux.org.uk> <20180826173236.GU6515@ZenIV.linux.org.uk> <20180826225749.GY6515@ZenIV.linux.org.uk> <20180828000310.GE6515@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180828000310.GE6515@ZenIV.linux.org.uk> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 28, 2018 at 01:03:10AM +0100, Al Viro wrote: > if (tcf_exts_get_net(&n->exts)) > tcf_queue_work(&n->rwork, u32_delete_key_freepf_work); > else > u32_destroy_key(n->tp, n, true); > ... and we hit u32_destroy_key(, , true), which does Speaking of which, we'd better never hit that branch for other reasons - there's no RCU delay between removal of knode from the hash chain and its kfree(). tcf_queue_work() does guarantee such delay (by use of queue_rcu_work()), direct call doesn't... Anyway, whichever branch is taken, the memory corruption problem remains - the comments below are accurate, AFAICS. > Incidentally, if we hit > tcf_queue_work(&n->rwork, u32_delete_key_freepf_work); > instead of u32_destroy_key(), the things don't seem to be any better - we > won't do anything to until rtnl is dropped, so u32_destroy() won't > break on the second pass through the loop - it'll free there and > return. Setting us up for trouble, since when u32_delete_key_freepf_work() > finally gets to u32_destroy_key() we'll have ->ht_down pointing > to freed memory and decrementing its contents...