From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C3E47C19F2B for ; Mon, 1 Aug 2022 14:37:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232570AbiHAOhi (ORCPT ); Mon, 1 Aug 2022 10:37:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49688 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230387AbiHAOhh (ORCPT ); Mon, 1 Aug 2022 10:37:37 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7A2D833368; Mon, 1 Aug 2022 07:37:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=FaVkEakWw5UkhKC0z7612iz8Sezsq/DZXrhQ3cY+yUw=; b=SAVLI21ATZ0FBXs5JGrzgiY8kR D3nAfI+mwkN2X3CVciMzhnRNeK0fE1T1BijkZDqOIIwU0O/QYFDZtbXIJcb68dwsEzKLH/wo3JgWH X0OGrqQJfPULEwbVEqXf4fWxoMNjHdFeN+cYMMZbPOw4GKwhgow0ux5Ewv9t5aBSZhemfTw/+rl5j jJMURX+yBxTbNqX/fJ7ja0ZdWzc4g188df9V61KvjCsflUbJkHZ5mnjQun2tpud6G111k8GPM39K6 zT7phs7VVtYeujVZJdpPjHXizMAEzvGPv1kvaYCJDKKqXvvjq/rs02cvLyRXnG0ml/SIq2RmbGqDa Ei7zY8xw==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1oIWXg-007Aot-Ki; Mon, 01 Aug 2022 14:37:12 +0000 Date: Mon, 1 Aug 2022 15:37:12 +0100 From: Matthew Wilcox To: Mikulas Patocka Cc: Linus Torvalds , Will Deacon , "Paul E. McKenney" , Ard Biesheuvel , Alexander Viro , Alan Stern , Andrea Parri , Peter Zijlstra , Boqun Feng , Nicholas Piggin , David Howells , Jade Alglave , Luc Maranget , Akira Yokosawa , Daniel Lustig , Joel Fernandes , Linux Kernel Mailing List , linux-arch , linux-fsdevel@vger.kernel.org Subject: Re: [PATCH v4 2/2] change buffer_locked, so that it has acquire semantics Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, Aug 01, 2022 at 06:43:55AM -0400, Mikulas Patocka wrote: > Let's have a look at this piece of code in __bread_slow: > get_bh(bh); > bh->b_end_io = end_buffer_read_sync; > submit_bh(REQ_OP_READ, 0, bh); > wait_on_buffer(bh); > if (buffer_uptodate(bh)) > return bh; > Neither wait_on_buffer nor buffer_uptodate contain any memory barrier. > Consequently, if someone calls sb_bread and then reads the buffer data, > the read of buffer data may be executed before wait_on_buffer(bh) on > architectures with weak memory ordering and it may return invalid data. > > Fix this bug by changing the function buffer_locked to have the acquire > semantics - so that code that follows buffer_locked cannot be moved before > it. I think this is the wrong approach. Instead, buffer_set_uptodate() should have the smp_wmb() and buffer_uptodate should have the smp_rmb(). Just like the page flags. As I said last night.