All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+83693dbba860b4f2e549@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [reiserfs?] possible deadlock in chmod_common (2)
Date: Thu, 21 Dec 2023 19:06:58 -0800	[thread overview]
Message-ID: <0000000000006a3904060d1082e7@google.com> (raw)
In-Reply-To: <000000000000e32f3c0609cb98d0@google.com>

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

***

Subject: [reiserfs?] possible deadlock in chmod_common (2)
Author: lizhi.xu@windriver.com

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git aafe7ad77b91

diff --git a/fs/reiserfs/ioctl.c b/fs/reiserfs/ioctl.c
index dd33f8cc6eda..cf219a998a89 100644
--- a/fs/reiserfs/ioctl.c
+++ b/fs/reiserfs/ioctl.c
@@ -100,7 +100,9 @@ long reiserfs_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
 			err = -EPERM;
 			break;
 		}
+		reiserfs_write_unlock(inode->i_sb);
 		err = mnt_want_write_file(filp);
+		reiserfs_write_lock(inode->i_sb);
 		if (err)
 			break;
 		if (get_user(inode->i_generation, (int __user *)arg)) {

  parent reply	other threads:[~2023-12-22  3:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 12:38 [syzbot] [reiserfs?] possible deadlock in chmod_common (2) syzbot
2023-12-21  4:05 ` syzbot
2023-12-22  5:26   ` [PATCH arm64] reiserfs: fix deadlock in chmod_common Lizhi Xu
2023-12-22  3:06 ` syzbot [this message]
     [not found] <20231222030654.849208-1-lizhi.xu@windriver.com>
2023-12-22  4:19 ` [syzbot] [reiserfs?] possible deadlock in chmod_common (2) 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=0000000000006a3904060d1082e7@google.com \
    --to=syzbot+83693dbba860b4f2e549@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.