Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2000310yba; Thu, 25 Apr 2019 09:03:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqxvQPVvE9VYWxnbZNuAcgpELpwOOuMRxIi+M6ol0GlAXbz6JVcmVRrYuhLtCUjABK8SwbEh X-Received: by 2002:a62:1815:: with SMTP id 21mr41086400pfy.107.1556208230073; Thu, 25 Apr 2019 09:03:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556208230; cv=none; d=google.com; s=arc-20160816; b=A0mtoTCvctpC+vhqcr1CindVk5gmLWNNtNYdrTbwrZYgeO43gsgTT4ivpsRC7LgMh6 OJSvtcHH8jeB3XoQaINpD1oywIoNKVekkuWTJ4SFcQGiuxXqIZq3RIMa9287bEmyI59W brX50dwFEb68gyPdfAvFwHwbtpnaiuLmNEo3RwuHUgoGBR38rtVklyL4SM5I7c7keLOi FP8BlQWdk3lQgJpVrK2tw35/SP6sZ2qWhN/CY75G3erdTx4NzEdHZxNdxKK0mJk6KdDZ qHayVEbX4sakhnHZZjbdr2H7OxpNMnAJXWIweo1YbGEOjAatWGxKk7dXgNrudX2FvrIx VN0Q== 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:mail-followup-to :message-id:subject:cc:to:from:date; bh=p4rTP+TXCVlH7kuAZwRKJB6Sa3Ul+xYQqAcGwmRLFJg=; b=Cj9oZZ6YZ/vaHc5cmfgtlZUIOoNo5Uzz7y907tHOQRWCqhpT5eKi+EsjFX//h7fDbu qMHd8BYShJ0PSPVckCFddaRRs8WA9RRzgbVR9AmOaGbdZoxo8XVgTslBI/PBYxTXyYfY fQIgRmFosYJlnSzQmkjjeob7l4hDCb+Zxq4gaFrPV82+alkCS4hhJgWrbpaGoMJnwBHU ecAMjnTeJd0lj/mExxOgA8L9GnOo/xcD9G2rIZ1ZxwDYVn2F63l01iZTtSfyAaZMdTZE 11AsMe7oV99kQj+uGvzUwaNNRZvS4Wg/W+mTUVxBCFsHcee8barr5J+OyPzD/sGPH/Wu 0TQQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-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 i76si7746489pgd.558.2019.04.25.09.03.33; Thu, 25 Apr 2019 09:03:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727032AbfDYP55 (ORCPT + 99 others); Thu, 25 Apr 2019 11:57:57 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:45564 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726626AbfDYP55 (ORCPT ); Thu, 25 Apr 2019 11:57:57 -0400 Received: from callcc.thunk.org (guestnat-104-133-0-109.corp.google.com [104.133.0.109] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x3PFvkcD006799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 25 Apr 2019 11:57:47 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id D37DC420EEC; Thu, 25 Apr 2019 11:57:45 -0400 (EDT) Date: Thu, 25 Apr 2019 11:57:45 -0400 From: "Theodore Ts'o" To: Barret Rhoden Cc: Andreas Dilger , syzbot+f584efa0ac7213c226b7@syzkaller.appspotmail.com, Jan Kara , stable@vger.kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] ext4: fix use-after-free race with debug_want_extra_isize Message-ID: <20190425155745.GB4739@mit.edu> Mail-Followup-To: Theodore Ts'o , Barret Rhoden , Andreas Dilger , syzbot+f584efa0ac7213c226b7@syzkaller.appspotmail.com, Jan Kara , stable@vger.kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org References: <20190415211945.27343-1-brho@google.com> <20190418155937.164947-1-brho@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190418155937.164947-1-brho@google.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Thu, Apr 18, 2019 at 11:59:37AM -0400, Barret Rhoden wrote: > When remounting with debug_want_extra_isize, we were not performing the > same checks that we do during a normal mount. That allowed us to set a > value for s_want_extra_isize that reached outside the s_inode_size. > > Reported-by: syzbot+f584efa0ac7213c226b7@syzkaller.appspotmail.com > Reviewed-by: Jan Kara > Signed-off-by: Barret Rhoden > Cc: stable@vger.kernel.org # 4.14.111 Applied, thanks. - Ted