Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp5927649ybh; Wed, 7 Aug 2019 13:59:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqx/a9bBoWBk1w6Yc5810/tBaBpS2QT4s/qqkcOlxTy9oLQzKh1xUPRaY9Q71/sWCl4lXEha X-Received: by 2002:a63:9e43:: with SMTP id r3mr9597695pgo.148.1565211567469; Wed, 07 Aug 2019 13:59:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565211567; cv=none; d=google.com; s=arc-20160816; b=jTuUoFthuvX6WlbaivqruOWexOEQYXCws/C9IaC/FSolVKDIH8ZsgKI7xH7pB2JWIH y50C0EWEFK6d7ghETAIZTcbV0SP/tYaNtUkd8y84YpnUpFntkAGvWK5SO1B1GVbbUxFu kgIPnNlCr6dydJOxXAFFlfFE/lnnSOJEsHfzbR6dr1o7yioog7l1LEC/XLmHVo3vGTf5 ep/0HV9sHbgZDyxe8/GlJzMBogE7eR3yB/Qk7l2WkYe9pozjMUXj+2jS/tzMOSJHga+1 zUg6JNnRxv1o3CUOJVb3qsPJiZRe9sEC354KY2N159jLsst/NzR0NkPNZuI3brVDNPLX 8zfA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=WO636kN42lJ5e6s4wK+/oLawQj7mjT/l31TogY7ruaA=; b=oocGWQOvB/eaFyWrQi+8bsfXcusYoi7UFVyoVD11iDjqW1VTyfnmUnGFF8Y8TSWMab s7DZbNXZOVZtibkIX4aC9Hdtd67VmQGv7JFYc/PU7TklnaeyqpOft7+ydJ7lBIZIYsrM QEfdGzCS756bnDjYXq11mBOKjrmzR/bxfLNZvPB5HhdMK+KPhp02kKB3VhXpIpFLawbL YHWSZ/TGLU54Sml+2TomBc89TSynqpAP9yhqsjPE0XGcs9WqtnvVEJy9cBVdGz/07g/Y rwZ8mNqbIuWfowsBCvQe3p05QMf4LdAiP5juFW6RBWaSMw/2Q3gnF/JRO2z1iN0KrswM OYVA== 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 x21si35819281pgh.477.2019.08.07.13.59.11; Wed, 07 Aug 2019 13:59:27 -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 S2389166AbfHGUwq (ORCPT + 99 others); Wed, 7 Aug 2019 16:52:46 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:51681 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729712AbfHGUwp (ORCPT ); Wed, 7 Aug 2019 16:52:45 -0400 Received: from p200300ddd742df588d2c07822b9f4274.dip0.t-ipconnect.de ([2003:dd:d742:df58:8d2c:782:2b9f:4274]) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hvSvF-0006A9-Cj; Wed, 07 Aug 2019 22:52:38 +0200 Date: Wed, 7 Aug 2019 22:52:31 +0200 (CEST) From: Thomas Gleixner To: Austin Kim cc: Sebastian Andrzej Siewior , Sasha Levin , peterz@infradead.org, mingo@kernel.org, tj@kernel.org, jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, stable@vger.kernel.org, =?EUC-KR?B?I7ytx/zB+A==?= Subject: Re: NULL ptr deref in wq_worker_sleeping on 4.19 In-Reply-To: Message-ID: References: <20190719135352.GF4240@sasha-vm> <20190807114649.fjfaj4oytcxaua7o@linutronix.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 7 Aug 2019, Austin Kim wrote: Again: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top > Is it possible for you to generate kernel patch only with **kernel > log** for 'use-after-free' case? What? I have no idea how to reproduce that issue so how should I create a kernel patch for something which can happen at some random place in several million lines of code? > With kernel log, we only have limited information, so it is hard to > debug 'use-after-free' case with this signature. My information is even more limited... Thanks, tglx