mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	syzbot+a5d1c9dfa91705cd2f6d@syzkaller.appspotmail.com,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] Revert "fs/ntfs3: Replace inode_trylock with inode_lock"
Date: Mon, 7 Jul 2025 14:44:02 +0100	[thread overview]
Message-ID: <d18a4aa3-bd7d-4c4b-a34c-48ba7f907ecf@lucifer.local> (raw)
In-Reply-To: <20250707124738.6764-1-almaz.alexandrovich@paragon-software.com>

+cc hch given his response

On Mon, Jul 07, 2025 at 02:47:38PM +0200, Konstantin Komarov wrote:
> This reverts commit 69505fe98f198ee813898cbcaf6770949636430b.
>
> Make lock acquiring conditional to avoid the deadlock.
>
> Fixes: 69505fe98f19 ("fs/ntfs3: Replace inode_trylock with inode_lock")
> Reported-by: syzbot+a5d1c9dfa91705cd2f6d@syzkaller.appspotmail.com
> Suggested-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>

OK you made me have to go searching to figure out where I suggested this :) it
was in:

https://lore.kernel.org/all/2076fb41-4017-4ae4-99df-acfb6148a408@lucifer.local/

Which is in fact syzbot+a91fcdbd2698f99db8f4@syzkaller.appspotmail.com ...

I'm guessing the reported-by you've mentioned here is the same thing but would
have been helpful to link the original report.

Anyway I'm with Christoph here - your commit message is really not great,
esp. since you don't link the report where I provided you with an analysis.

So I suggest you:

- Summarise what I said there in commit message

- Provide a Reported-by tag for the syzkaller report I gave, since it's more
  useful than the other one (which is presumably a dupe anyway)

- Provide a Closes tag linking that report so it's easy for people to see.

Thanks!

> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> ---
>  fs/ntfs3/file.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
> index 65fb27d1e17c..2e321b84a1ed 100644
> --- a/fs/ntfs3/file.c
> +++ b/fs/ntfs3/file.c
> @@ -322,7 +322,10 @@ static int ntfs_file_mmap(struct file *file, struct vm_area_struct *vma)
>  		}
>
>  		if (ni->i_valid < to) {
> -			inode_lock(inode);
> +			if (!inode_trylock(inode)) {
> +				err = -EAGAIN;
> +				goto out;
> +			}
>  			err = ntfs_extend_initialized_size(file, ni,
>  							   ni->i_valid, to);
>  			inode_unlock(inode);
> --
> 2.43.0
>

  parent reply	other threads:[~2025-07-07 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 12:47 Konstantin Komarov
2025-07-07 13:00 ` Christoph Hellwig
2025-07-07 13:44 ` Lorenzo Stoakes [this message]
2025-07-08  7:57   ` [PATCH v2] " Konstantin Komarov
2025-07-09 14:16     ` Lorenzo Stoakes

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=d18a4aa3-bd7d-4c4b-a34c-48ba7f907ecf@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzbot+a5d1c9dfa91705cd2f6d@syzkaller.appspotmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®