From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 58E98FBF2 for ; Tue, 2 Jan 2024 13:35:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f70.google.com with SMTP id ca18e2360f4ac-7b7fef9ef2aso1203400439f.2 for ; Tue, 02 Jan 2024 05:35:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704202516; x=1704807316; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=hEPAjr2Ytd+XVdWmKta/TmOX+0CoWkrwQ31hsDPS7O8=; b=F7uhkA8ZNPOLzAhGk0Wtjt6elfcF+ofGpbnQpUHbFEq4Lb7CPncAh7CyUPS6o0o9fU wHc35VAdgz4PSegngrye+4c/tXomHZfiChZ4z3qL6rg3CSJ9nU1xc3/DaH5FU1/HrbN9 imWevFca/n/miMShPt4hdSK1pT5bekNiLoedDdb+DMgzLaf3/NP3RMYGke6Elkdl7h9n fFrqBP8HK+8ggkGvnQIlbVBYyE7bV+SYooQULPKDqqdN8qJdTf709CJHhgeKdZpFZMJO J/Itlp5LTYmDkbZtEwBqAI6UlMGv2N/j9QR9+QQi9u6U/9B0uSZltZv1yMbA8+7DgZFS AjiQ== X-Gm-Message-State: AOJu0YxRBK8lBGTa8kQUV5a9Jkh5mhiSHRM8IglLR9yf+502AZnEaBcX MSVERQsea9JkNrDPcspf1a7J9UZ/pRoBgZ8bfGycxC9zlZUl X-Google-Smtp-Source: AGHT+IFgPKX0w7t+hcn0UpaleoH/hrZqqyklAqoisSpD6EBcrA4ukjJOBHKHPP89RSoNw8w3udtMT7TB3j5Fp5qCRLlrkr6yMx0U Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6602:2a44:b0:7ba:9c66:6d11 with SMTP id k4-20020a0566022a4400b007ba9c666d11mr734766iov.1.1704202516630; Tue, 02 Jan 2024 05:35:16 -0800 (PST) Date: Tue, 02 Jan 2024 05:35:16 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000a11763060df691a7@google.com> Subject: [syzbot] Monthly nilfs report (Jan 2024) From: syzbot To: konishi.ryusuke@gmail.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello nilfs maintainers/developers, This is a 31-day syzbot report for the nilfs subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/nilfs During the period, 1 new issues were detected and 1 were fixed. In total, 7 issues are still open and 37 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 444 Yes kernel BUG at fs/buffer.c:LINE! https://syzkaller.appspot.com/bug?extid=cfed5b56649bddf80d6e <2> 15 No KMSAN: uninit-value in nilfs_add_checksums_on_logs (2) https://syzkaller.appspot.com/bug?extid=47a017c46edb25eff048 <3> 6 Yes kernel BUG in end_buffer_async_write https://syzkaller.appspot.com/bug?extid=5c04210f7c7f897c1e7f <4> 1 No possible deadlock in nilfs_dirty_inode (2) https://syzkaller.appspot.com/bug?extid=903350d47ddb4cbb7f6f --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@googlegroups.com. To disable reminders for individual bugs, reply with the following command: #syz set no-reminders To change bug's subsystems, reply with: #syz set subsystems: new-subsystem You may send multiple commands in a single email message.