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 973F1C4332F for ; Wed, 6 Apr 2022 00:27:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1588854AbiDFARh (ORCPT ); Tue, 5 Apr 2022 20:17:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243504AbiDEKgt (ORCPT ); Tue, 5 Apr 2022 06:36:49 -0400 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1393654BED for ; Tue, 5 Apr 2022 03:22:26 -0700 (PDT) Received: by mail-il1-f200.google.com with SMTP id s14-20020a056e021a0e00b002c7c03a5d81so7856796ild.9 for ; Tue, 05 Apr 2022 03:22:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:in-reply-to:message-id:subject :from:to:cc; bh=KgDEWNq4Hu6J0g2sltSIO9az7ceb9wGnxRPSlOiKDKI=; b=kKBmjDlNQ+TatgPlMdAvnMDspRXOVkyGAJ5w281qkqiVTre/7G7WSruUe5eiqN6brY RpqANGsyKtfNrhnWplzsACvCnAmgVHWSISqrEBNGDlchYmT65cryHxSuaG7aGU6qUXxk 7LecDccZrPDH204tt5z8xdsVKY46cDaet3ye5+DXdoL+jaAp0C4NRyz3M4CbXeuf/OGd hZaV4GTMCdFzeqccoif4qISb0kQcQ9QQFM/pRAss1m94Z4OgS5yED6zf40O+khp9efeF xJrsTpDpftOIWAQlxsgectFtCaEQYKEZ/hMHjnUJzlDtFe5Ly7FIylhdnbjCxmgptNud Vu9g== X-Gm-Message-State: AOAM532m9Usp47eDE1NsYXKgnnp1pXgri5D3HDshzm/AGOYQYVuPlTpw cQ8DA42Z4ReJjHAj55aXtoEleRoZcUZFS0qCItptwjicFz8U X-Google-Smtp-Source: ABdhPJwOPGrLRPS+Xez4lqD8aEH/TLyFtBjHatL1toVbcjfEiZ4o0aDloyMpdCxlcQHleIPbCcbk9Gq6jIdkg0jifHvC0ghOiqbX MIME-Version: 1.0 X-Received: by 2002:a05:6e02:216f:b0:2ca:203b:75d with SMTP id s15-20020a056e02216f00b002ca203b075dmr1310884ilv.174.1649154145537; Tue, 05 Apr 2022 03:22:25 -0700 (PDT) Date: Tue, 05 Apr 2022 03:22:25 -0700 In-Reply-To: <20220405070312.900870293@linuxfoundation.org> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000000654d905dbe59ff2@google.com> Subject: Re: [PATCH 5.10 473/599] ext4: dont BUG if someone dirty pages without asking ext4 first From: syzbot To: Greg Kroah-Hartman Cc: gregkh@linuxfoundation.org, lee.jones@linaro.org, linux-kernel@vger.kernel.org, sashal@kernel.org, stable@vger.kernel.org, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > From: Theodore Ts'o > > [ Upstream commit cc5095747edfb054ca2068d01af20be3fcc3634f ] > > [un]pin_user_pages_remote is dirtying pages without properly warning > the file system in advance. A related race was noted by Jan Kara in > 2018[1]; however, more recently instead of it being a very hard-to-hit > race, it could be reliably triggered by process_vm_writev(2) which was > discovered by Syzbot[2]. > > This is technically a bug in mm/gup.c, but arguably ext4 is fragile in > that if some other kernel subsystem dirty pages without properly > notifying the file system using page_mkwrite(), ext4 will BUG, while > other file systems will not BUG (although data will still be lost). > > So instead of crashing with a BUG, issue a warning (since there may be > potential data loss) and just mark the page as clean to avoid > unprivileged denial of service attacks until the problem can be > properly fixed. More discussion and background can be found in the > thread starting at [2]. > > [1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz > [2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com > > Reported-by: syzbot+d59332e2db681cf18f0318a06e994ebbb529a8db@syzkaller.appspotmail.com > Reported-by: Lee Jones > Signed-off-by: Theodore Ts'o > Link: https://lore.kernel.org/r/YiDS9wVfq4mM2jGK@mit.edu > Signed-off-by: Sasha Levin > --- > fs/ext4/inode.c | 25 +++++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c > index d59474a54189..96546df39bcf 100644 > --- a/fs/ext4/inode.c > +++ b/fs/ext4/inode.c > @@ -2023,6 +2023,15 @@ static int ext4_writepage(struct page *page, > else > len = PAGE_SIZE; > > + /* Should never happen but for bugs in other kernel subsystems */ > + if (!page_has_buffers(page)) { > + ext4_warning_inode(inode, > + "page %lu does not have buffers attached", page->index); > + ClearPageDirty(page); > + unlock_page(page); > + return 0; > + } > + > page_bufs = page_buffers(page); > /* > * We cannot do block allocation or other extent handling in this > @@ -2626,6 +2635,22 @@ static int mpage_prepare_extent_to_map(struct mpage_da_data *mpd) > wait_on_page_writeback(page); > BUG_ON(PageWriteback(page)); > > + /* > + * Should never happen but for buggy code in > + * other subsystems that call > + * set_page_dirty() without properly warning > + * the file system first. See [1] for more > + * information. > + * > + * [1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz > + */ > + if (!page_has_buffers(page)) { > + ext4_warning_inode(mpd->inode, "page %lu does not have buffers attached", page->index); > + ClearPageDirty(page); > + unlock_page(page); > + continue; > + } > + > if (mpd->map.m_len == 0) > mpd->first_page = page->index; > mpd->next_page = page->index + 1; > -- > 2.34.1 > > > I see the command but can't find the corresponding bug. The email is sent to syzbot+HASH@syzkaller.appspotmail.com address but the HASH does not correspond to any known bug. Please double check the address.