From nobody Fri Apr 17 20:37:11 2026 Received: from mail-oo1-f71.google.com (mail-oo1-f71.google.com [209.85.161.71]) (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 C3B658632A for ; Sat, 14 Feb 2026 12:05:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.71 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771070756; cv=none; b=NfsMbCrn2F6smVwMklPM6LSxeLFizd3n8jw6HHMMCWo4tOUa4vJzAyPTOA5Plyf0iwvYT9v0/u6BKZ053fdSQJsxMHkzelGEghxgIDSDbPCrdP8bZzNd0fetxZzPjaky77ii8ED2wv27J8B6zk8Hk5+Uzs1LdVcMo26AHpO3ArI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771070756; c=relaxed/simple; bh=qqY36xdQ22aanCmyrJwTMxH0V9xdZ57CzJyduSvOXic=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=HzKOQ1NRx4wXshw6u47c/a537IKOxlf2nvuA6uXoe+xUNCH6PTIsmj3i6pyJzb29v+Uz/t3XEy00m0VmnLWSuXdmILNja+0Ft20h0Brr9c7P3iIDlpdz+pTWRWf560TdeGKNwJBwGN1zAY/V2SW5xiCQZf99h6SYBwEk+syi+pQ= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.71 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-oo1-f71.google.com with SMTP id 006d021491bc7-672c40f3873so15488039eaf.2 for ; Sat, 14 Feb 2026 04:05:54 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771070754; x=1771675554; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=BpSEuNe7MWt5s5ME9BTrEG5W/cpomoP+P7lBmgKdsdk=; b=CzT7LYUhXNlDeIKe/+8a+cHggVkZ3TsrpLyd7hvuXg65D3gQrJG49/uODyh+/xTdAh wOTE1YOJ1nC+MHd4HMcGx4jfX+MX8INRiWUqsXeX5at95QodLw0n+lsAot4nRZaRC8lv vYxDGOVJsLDEU8fZMSX23q4Xo08bU6TyuqJql7Ak2YMk2ZgAlAVtkS+27WERf7Q0Kb1z lcjq4pMgCDDYaKG+XSBgMAdZTObEJE97Xb8PYYGW9+jNceXdrjgFs6LHJbsukKSpcLmA rOGEV7HfazZxPqPAtc1QDTLEmM7kKhqv6uTfb3teS69OCRX56TnXYJXZrA0zvo4rIRPH 4oPg== X-Gm-Message-State: AOJu0YwmzvFl7j5t+W5Npp8dBKG6/HEyTMS3UO7v8J1H97vSdGKx28br Qu45QMpbvkHBvANtiin8wqeD4e2tRDSYSv03DP83N06XplIXG/GH3PINSLYaVtnlkHIGwSWO1jJ 3EIHS4omQY8ruFysGpDyAa16cIg6KS3xheCyXvXESWELYNSF9vd6aZhrgCA4= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:2297:b0:679:a9:9447 with SMTP id 006d021491bc7-67900a9990cmr369658eaf.27.1771070753755; Sat, 14 Feb 2026 04:05:53 -0800 (PST) Date: Sat, 14 Feb 2026 04:05:53 -0800 In-Reply-To: <699000b2.050a0220.3a4a67.00a6.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69906521.a70a0220.3c8f9c.0090.GAE@google.com> Subject: Forwarded: Private message regarding: [syzbot] [xfs?] inconsistent lock state in igrab From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: Private message regarding: [syzbot] [xfs?] inconsistent lock state= in igrab Author: kapoorarnav43@gmail.com #syz test=20 From 7e7a6c0e2d9a2d7b9f9a4f5b1b0f2a1c7f0a1234 Mon Sep 17 00:00:00 2001 From: Arnav Kapoor Date: Sat, 14 Feb 2026 17:35:00 +0000 Subject: [PATCH] fs: fserror: avoid igrab in atomic contexts MIME-Version: 1.0 Content-Type: text/plain; charset=3DUTF-8 Content-Transfer-Encoding: 8bit fserror_report() can be called from softirq/atomic contexts. Using igrab() there takes i_lock, which is also acquired with softirqs enabled in process context, triggering lockdep warnings and a potential softirq recursion deadlock. All fserror_report() callers already hold a live reference to the inode, so use ihold() to take a safe reference without grabbing i_lock. Reported-by: syzbot+5eb0d61dfb76ca12670c@syzkaller.appspotmail.com Signed-off-by: Arnav Kapoor --- fs/fserror.c | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/fs/fserror.c b/fs/fserror.c index 0123456789ab..fedcba987654 100644 --- a/fs/fserror.c +++ b/fs/fserror.c @@ -159,16 +159,13 @@ void fserror_report(struct super_block *sb, struct=20 inode *inode, event->len =3D len; event->error =3D error; /* - * Can't iput from non-sleeping context, so grabbing another reference - * to the inode must be the last thing before submitting the event. + * Can't iput from non-sleeping context, so grabbing another reference + * to the inode must be the last thing before submitting the event. + * The caller must hold a live reference if @inode is provided. */ if (inode) { - event->inode =3D igrab(inode); - if (!event->inode) - goto lost_event; + ihold(inode); + event->inode =3D inode; } /* @@ -184,9 +181,7 @@ void fserror_report(struct super_block *sb, struct=20 inode *inode, schedule_work(&event->work); return; -lost_event: - fserror_free_event(event); lost: if (inode) pr_err_ratelimited("%s: lost file I/O error report for ino %lu=20 type %u pos 0x%llx len 0x%llx error %d", -- 2.43.0 On Saturday, 14 February 2026 at 17:32:10 UTC+5:30 syzbot wrote: Hello,=20 syzbot tried to test the proposed patch but the build/boot failed:=20 failed to apply patch:=20 checking file fs/fserror.c=20 patch: **** unexpected end of file in patch=20 Tested on:=20 commit: 770aaedb Merge tag 'bootconfig-v7.0' of git://git.kern..=20 git tree: upstream=20 kernel config: https://syzkaller.appspot.com/x/.config?x=3De600149b13c010eb=20 dashboard link: https://syzkaller.appspot.com/bug?extid=3D5eb0d61dfb76ca126= 70c=20 compiler:=20 patch: https://syzkaller.appspot.com/x/patch.diff?x=3D15adac02580000