From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965118AbcCNNxM (ORCPT ); Mon, 14 Mar 2016 09:53:12 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:33914 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964973AbcCNNxJ (ORCPT ); Mon, 14 Mar 2016 09:53:09 -0400 Date: Mon, 14 Mar 2016 14:54:21 +0100 From: Miklos Szeredi To: Seth Forshee Cc: m.loschwitz@syseleven.de, robert@quobyte.com, fuse-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] fuse: do not use iocb after it may have been freed Message-ID: <20160314135421.GO8655@tucsk> References: <1457714135-50289-1-git-send-email-seth.forshee@canonical.com> <1457714135-50289-2-git-send-email-seth.forshee@canonical.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1457714135-50289-2-git-send-email-seth.forshee@canonical.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 11, 2016 at 10:35:33AM -0600, Seth Forshee wrote: > From: Robert Doebbelin > > Reading wrong data may cause the IO thread to starve waiting for completion. > The issue was introduced with commit 04b2fa9 and thus affects kernel >= 4.1. It > was discovered by KASan: Thanks, queued. Miklos