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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C4040C001DC for ; Mon, 31 Jul 2023 10:58:33 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4RDwG0297vz301T for ; Mon, 31 Jul 2023 20:58:32 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=linux.alibaba.com (client-ip=115.124.30.113; helo=out30-113.freemail.mail.aliyun.com; envelope-from=hsiangkao@linux.alibaba.com; receiver=lists.ozlabs.org) Received: from out30-113.freemail.mail.aliyun.com (out30-113.freemail.mail.aliyun.com [115.124.30.113]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4RDwFr0z2nz2y1d for ; Mon, 31 Jul 2023 20:58:22 +1000 (AEST) X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R131e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046051;MF=hsiangkao@linux.alibaba.com;NM=1;PH=DS;RN=14;SR=0;TI=SMTPD_---0Voe5MEo_1690801095; Received: from 10.120.130.14(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0Voe5MEo_1690801095) by smtp.aliyun-inc.com; Mon, 31 Jul 2023 18:58:17 +0800 Message-ID: <9b57e5f7-62b6-fd65-4dac-a71c9dc08abc@linux.alibaba.com> Date: Mon, 31 Jul 2023 18:58:14 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [syzbot] [erofs?] [fat?] WARNING in erofs_kill_sb To: Christoph Hellwig , syzbot References: <000000000000f43cab0601c3c902@google.com> <20230731093744.GA1788@lst.de> From: Gao Xiang In-Reply-To: <20230731093744.GA1788@lst.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: linux-erofs@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development of Linux EROFS file system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: brauner@kernel.org, jack@suse.cz, syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, huyue2@coolpad.com, sj1557.seo@samsung.com, linux-erofs@lists.ozlabs.org, linkinjeon@kernel.org Errors-To: linux-erofs-bounces+linux-erofs=archiver.kernel.org@lists.ozlabs.org Sender: "Linux-erofs" On 2023/7/31 17:37, Christoph Hellwig wrote: > On Mon, Jul 31, 2023 at 12:57:58AM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following issue on: >> >> HEAD commit: d7b3af5a77e8 Add linux-next specific files for 20230728 > > Hmm, the current linux-next tree does not seem to have that commit ID > any more, and the line numbers don't match up. I think it is the > WARN_ON for the magic, which could probably be just removed. I'll > try the reproducers when I find a bit more time. Previously, deactivate_locked_super() or .kill_sb() will only be called after fill_super is called, and .s_magic will be set at the very beginning of erofs_fc_fill_super(). After ("fs: open block device after superblock creation"), such convension is changed now. Yet at a quick glance, WARN_ON(sb->s_magic != EROFS_SUPER_MAGIC); in erofs_kill_sb() can be removed since deactivate_locked_super() will also be called if setup_bdev_super() is falled. I'd suggest that removing this WARN_ON() in the related commit, or as a following commit of the related branch of the pull request if possible. Thanks, Gao Xiang 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 DC455C00528 for ; Mon, 31 Jul 2023 10:59:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231952AbjGaK7A (ORCPT ); Mon, 31 Jul 2023 06:59:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231308AbjGaK6l (ORCPT ); Mon, 31 Jul 2023 06:58:41 -0400 Received: from out30-97.freemail.mail.aliyun.com (out30-97.freemail.mail.aliyun.com [115.124.30.97]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B4EC419A4; Mon, 31 Jul 2023 03:58:20 -0700 (PDT) X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R131e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018046051;MF=hsiangkao@linux.alibaba.com;NM=1;PH=DS;RN=14;SR=0;TI=SMTPD_---0Voe5MEo_1690801095; Received: from 10.120.130.14(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0Voe5MEo_1690801095) by smtp.aliyun-inc.com; Mon, 31 Jul 2023 18:58:17 +0800 Message-ID: <9b57e5f7-62b6-fd65-4dac-a71c9dc08abc@linux.alibaba.com> Date: Mon, 31 Jul 2023 18:58:14 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [syzbot] [erofs?] [fat?] WARNING in erofs_kill_sb To: Christoph Hellwig , syzbot Cc: brauner@kernel.org, chao@kernel.org, huyue2@coolpad.com, jack@suse.cz, jefflexu@linux.alibaba.com, linkinjeon@kernel.org, linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, sj1557.seo@samsung.com, syzkaller-bugs@googlegroups.com, xiang@kernel.org References: <000000000000f43cab0601c3c902@google.com> <20230731093744.GA1788@lst.de> From: Gao Xiang In-Reply-To: <20230731093744.GA1788@lst.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On 2023/7/31 17:37, Christoph Hellwig wrote: > On Mon, Jul 31, 2023 at 12:57:58AM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following issue on: >> >> HEAD commit: d7b3af5a77e8 Add linux-next specific files for 20230728 > > Hmm, the current linux-next tree does not seem to have that commit ID > any more, and the line numbers don't match up. I think it is the > WARN_ON for the magic, which could probably be just removed. I'll > try the reproducers when I find a bit more time. Previously, deactivate_locked_super() or .kill_sb() will only be called after fill_super is called, and .s_magic will be set at the very beginning of erofs_fc_fill_super(). After ("fs: open block device after superblock creation"), such convension is changed now. Yet at a quick glance, WARN_ON(sb->s_magic != EROFS_SUPER_MAGIC); in erofs_kill_sb() can be removed since deactivate_locked_super() will also be called if setup_bdev_super() is falled. I'd suggest that removing this WARN_ON() in the related commit, or as a following commit of the related branch of the pull request if possible. Thanks, Gao Xiang