Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3799457ybl; Tue, 20 Aug 2019 02:25:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmi5WEmnXxYSBqKnnWn89G4y2301in0f6Ub7rVxMGDWonD91EqZXBbdAab8DSMC88RJ59P X-Received: by 2002:aa7:8392:: with SMTP id u18mr29245017pfm.72.1566293104692; Tue, 20 Aug 2019 02:25:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566293104; cv=none; d=google.com; s=arc-20160816; b=Tn2/lwLWUrfF5TqiE+ad9XXYCTDzuUdFbiUf/+hj3jclab+A2yErfhS2ZqPwyqKEZ0 0PqV7L5o0OvCKV1Xgnoi36bH2GhAttO76Nmqlcmov5dAou3mMgM4pg468BaAZKAd+i05 /HTZCijEFzpP8V0wpOflolCkbkw9vgzXfwAXJSGpglou6y+dAHEHdGaX7HUwLT7vqWVP 9D3jEaHTc94bmEya/pG7ZQzCAbwh/KVid9Zw9tb2gGaHGNN+alkQ9yuZyq3oJO7HQRiT OuVOnUN9raeTYQk+mbCzfDnzYZlHYktjI2EakVY8yepGQss2hFSIliIvKbvZIAvZg8iI MXCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=WujdHSp7eBH8ZQAY1yJcicySmCdXWUPmerli84SHLEc=; b=A6ho7cwwFTt0QbZaZ6JThAb85RpMjrHhmPADnavt6RWcg0QE6Z3P7ZK3JUdgnpN7YH 0UKhBbV8wVzrLMeS7VBLzqOZwFMyDrv2WUHkq4gJJDyMTQcKB7iMEubOE3x1IShQtX+R EkjHATVIMYouTCZVKzobf3kVGe1IebUBcOUi5PXhVJWCir8JDbZAhJo7Kqpw0Uwg4pO9 Jfw02mQkoX0rG7jTN4ykVzq27fBJIx/ViQZE8nu1VTUMHDZVd1kWkLfWWMfH1Lk+kVm0 aBRvkjJd4JxNJd4R8PSMhXrUnXFqDbO5jHg+GbGLOH7xG3dUn/+gvPx0Mt7B6jM194zM DpcQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a18si3553493pfa.177.2019.08.20.02.24.50; Tue, 20 Aug 2019 02:25:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729447AbfHTJXk (ORCPT + 99 others); Tue, 20 Aug 2019 05:23:40 -0400 Received: from mx2.suse.de ([195.135.220.15]:41692 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729210AbfHTJXk (ORCPT ); Tue, 20 Aug 2019 05:23:40 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BEFE9AE9A; Tue, 20 Aug 2019 09:23:38 +0000 (UTC) Date: Tue, 20 Aug 2019 11:23:37 +0200 From: Petr Mladek To: John Ogness Cc: linux-kernel@vger.kernel.org, Andrea Parri , Sergey Senozhatsky , Sergey Senozhatsky , Steven Rostedt , Brendan Higgins , Peter Zijlstra , Thomas Gleixner , Linus Torvalds , Greg Kroah-Hartman Subject: Re: [RFC PATCH v4 4/9] printk-rb: initialize new descriptors as invalid Message-ID: <20190820092337.cudkfdfhsu44vlhh@pathway.suse.cz> References: <20190807222634.1723-1-john.ogness@linutronix.de> <20190807222634.1723-5-john.ogness@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190807222634.1723-5-john.ogness@linutronix.de> User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 2019-08-08 00:32:29, John Ogness wrote: > Initialize never-used descriptors as permanently invalid so there The word "permanently" is confusing. It suggests that it will never ever be valid again. I would just remove the word. > is no risk of the descriptor unexpectedly being determined as > valid due to dataring head overflowing/wrapping. Please, provide more details about the solved race. Is it because some reader could have reference to an invalid (reused) descriptor? Can be these invalid descriptors be member of the list? Also it might be worth to mention where is the check that might detect such invalid descriptors and what will be the consequences. Well, this might be clear from the race description. Best Regards, Petr