Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1262405ybb; Fri, 3 Apr 2020 23:21:30 -0700 (PDT) X-Google-Smtp-Source: APiQypIs5TCioJ065SwJF2GWDYC5FLm+qrN1qtYS0YOcAGeaiAzfpMNYe+iZ/E5IxpEHEnpwm4a+ X-Received: by 2002:aca:df45:: with SMTP id w66mr2663082oig.76.1585981289975; Fri, 03 Apr 2020 23:21:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585981289; cv=none; d=google.com; s=arc-20160816; b=BK+sbzok4feB2Hqyc+LcT+W/p+t+mmbDpynTH3PR0/jX3YQX3FSK+aNoUPFl4zjhnf pNsQSaWAdZqASODxw3noZ2yD+sapejhmOcmnLqT/HM5H2gXELs3vBUIMm6bHCnIlg2fM 58CJex9bSXGfg2p3IZX4t6HlNn3uD27T95NfWFT+0MQyxvAWX7gUhV42ZXujbF6D2aEy C8/LBDfVqoTgIXlsUifljL2WbTaTz3hdoBqlVfRg94AEXpB7/A3YNkR/LCRztLagVCNw yGKBMNfS2kTFG+iwUSMjJaKJwPeK0XCBmLKOa+3Xbi8Elg7TG78jLIHhU5MOZxXULiic mjZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from; bh=DyhWYJ+QQWeZWPFmA9C+tADLCdhsrb7DPiDVgGUxkCA=; b=dPwUlCYsz7Xu8BjuC+m889axJ6Zt08LWbDtyUIRXU2kjDVnnmxfDk5LZgoHGeVvPjr xkl4W6K+Po0dbGFg35qgNauCzAbI12a70ceo6sj1d8lRUkGQwHTbuJtEpAhhVJ0gBxbb +GNUuijbhxnlFvv9hxE7MQ+hzbvi/Y0AOM+C4THWOdfCD691q4ncds/DMvFWR0/i2B0b E9yk7sAPIzuFFcslGn/CjnAhkcQZaLhnVW1eVeywoXNYap0nIGdJX2NxBUXsGmlBhEjS V/nfc0+1QgcsJvA10DoUH1CncJglmVjuXFX7xqrV9X7gAYDzAUmqfNCHX4qXs/Mby5rn FCBA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 a206si4642485oii.132.2020.04.03.23.21.02; Fri, 03 Apr 2020 23:21:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725933AbgDDGOI (ORCPT + 99 others); Sat, 4 Apr 2020 02:14:08 -0400 Received: from mail.parknet.co.jp ([210.171.160.6]:36796 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725536AbgDDGOI (ORCPT ); Sat, 4 Apr 2020 02:14:08 -0400 Received: from ibmpc.myhome.or.jp (server.parknet.ne.jp [210.171.168.39]) by mail.parknet.co.jp (Postfix) with ESMTPSA id 0FE2A12F211; Sat, 4 Apr 2020 15:14:07 +0900 (JST) Received: from devron.myhome.or.jp (foobar@devron.myhome.or.jp [192.168.0.3]) by ibmpc.myhome.or.jp (8.15.2/8.15.2/Debian-18) with ESMTPS id 0346E5Hb047956 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sat, 4 Apr 2020 15:14:06 +0900 Received: from devron.myhome.or.jp (foobar@localhost [127.0.0.1]) by devron.myhome.or.jp (8.15.2/8.15.2/Debian-18) with ESMTPS id 0346E5xb200873 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Sat, 4 Apr 2020 15:14:05 +0900 Received: (from hirofumi@localhost) by devron.myhome.or.jp (8.15.2/8.15.2/Submit) id 0346E2M4200872; Sat, 4 Apr 2020 15:14:02 +0900 From: OGAWA Hirofumi To: Dmitry Vyukov Cc: syzbot , Marco Elver , LKML , syzkaller-bugs Subject: Re: KCSAN: data-race in __fat_write_inode / fat12_ent_get References: <0000000000000cfff005a26226ce@google.com> <874ku0sncc.fsf@mail.parknet.co.jp> Date: Sat, 04 Apr 2020 15:14:02 +0900 In-Reply-To: (Dmitry Vyukov's message of "Fri, 3 Apr 2020 18:36:26 +0200") Message-ID: <877dyveq1h.fsf@mail.parknet.co.jp> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dmitry Vyukov writes: > On Fri, Apr 3, 2020 at 3:36 PM OGAWA Hirofumi > wrote: >> >> Hm, looks like the race between a directory entry vs a FAT entry. This >> bug was happened with the corrupted image? Or the image passes the check >> of dosfsck? >> >> If the corrupted image, it may be hard to prevent the all races. Well, >> anyway, the corrupted image of the report will help to detect this >> corruption. > > From the log, it's this program. > My bet on a corrupted image. syzkaller does not have format > descriptions for fat, so it's just random bytes. You meant I can regenerate a disk image from that log (if so, how)? If not, for next time, it would be helpful if syzkaller provides the log to regenerate the corrupted image (or saving a corrupted image) to reproduce this, then I can try to detect the corruption pattern early. Thanks. -- OGAWA Hirofumi