All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Syzbot test for v2: ocfs2: clear lock identity upon inode eviction
Date: Sun, 22 Feb 2026 20:31:28 -0800	[thread overview]
Message-ID: <699bd820.a70a0220.2c38d7.018f.GAE@google.com> (raw)
In-Reply-To: <66fdfef3.050a0220.9ec68.0031.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Syzbot test for v2: ocfs2: clear lock identity upon inode eviction
Author: activprithvi@gmail.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git c22e26bd0906e9c8325462993f01adb16b8ea2c0

Signed-off-by: Prithvi Tambewagh <activprithvi@gmail.com>
---
 fs/ocfs2/aops.c  | 5 +++++
 fs/ocfs2/inode.c | 1 +
 2 files changed, 6 insertions(+)

diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c
index 586e3b74d782..54261d7c14fa 100644
--- a/fs/ocfs2/aops.c
+++ b/fs/ocfs2/aops.c
@@ -2420,6 +2420,11 @@ static ssize_t ocfs2_direct_IO(struct kiocb *iocb, struct iov_iter *iter)
 	struct inode *inode = file->f_mapping->host;
 	struct ocfs2_super *osb = OCFS2_SB(inode->i_sb);
 	get_block_t *get_block;
+	if (IS_NOQUOTA(inode)) {
+		mlog(ML_ERROR, "Direct IO is not allowed for Quota inode %lu\n",
+		     inode->i_ino);
+		return -EPERM;
+	}
 
 	/*
 	 * Fallback to buffered I/O if we see an inode without
diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
index fcc89856ab95..e5d932914b70 100644
--- a/fs/ocfs2/inode.c
+++ b/fs/ocfs2/inode.c
@@ -1266,6 +1266,7 @@ static void ocfs2_clear_inode(struct inode *inode)
 			"Clear inode of %llu, alloc_sem is locked\n",
 			(unsigned long long)oi->ip_blkno);
 	up_write(&oi->ip_alloc_sem);
+	init_rwsem(&oi->ip_alloc_sem);
 
 	mlog_bug_on_msg(oi->ip_open_count,
 			"Clear inode of %llu has open count %d\n",
-- 
2.34.1


  parent reply	other threads:[~2026-02-23  4:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03  2:18 [syzbot] [ocfs2?] possible deadlock in ocfs2_del_inode_from_orphan syzbot
2024-12-19  8:16 ` syzbot
2026-01-06 11:30 ` Syzbot test for ocfs2: Fix " Prithvi Tambewagh
2026-01-06 11:59   ` [syzbot] [ocfs2?] possible " syzbot
2026-02-23  3:38 ` Forwarded: Syzbot test for v2: ocfs2: clear lock identity upon inode eviction syzbot
2026-02-23  4:31 ` syzbot [this message]
2026-02-24  5:28 ` Forwarded: test patch syzbot
2026-02-24  6:35 ` syzbot
2026-03-02  5:31 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=699bd820.a70a0220.2c38d7.018f.GAE@google.com \
    --to=syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.