From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:42337 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbeDERNn (ORCPT ); Thu, 5 Apr 2018 13:13:43 -0400 Date: Thu, 5 Apr 2018 19:11:14 +0200 From: David Sterba To: Sasha Levin Cc: Liu Bo , "linux-btrfs@vger.kernel.org" , "stable@vger.kernel.org" Subject: Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items Message-ID: <20180405171114.GL2635@twin.jikos.cz> Reply-To: dsterba@suse.cz References: <1522691988-127156-1-git-send-email-bo.liu@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Thu, Apr 05, 2018 at 04:42:34PM +0000, Sasha Levin wrote: > Hi. > > [This is an automated email] > > This commit has been processed by the -stable helper bot and determined > to be a high probability candidate for -stable trees. (score: 9.9156) > > The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126, > > v4.15.15: Build OK! > v4.14.32: Build OK! > v4.9.92: Build OK! > v4.4.126: Build OK! > > Please let us know if you'd like to have this patch included in a stable tree. Yes, in this case we expect that the Fixes: tag will let the patch flow to stable after it gets applied to master. The automated stable candidate patch scanning would be helpful in cases where the Fixes tag is not identified or we forget to add it. I don't mind helping to train the bot, so I'll try respond to the messages.