From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Suraj Jitindar Singh <surajjs@amazon.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] fs/ntfs3: Additional check in ntfs_file_release
Date: Sat, 25 Jan 2025 09:03:50 -0500 [thread overview]
Message-ID: <20250124202058-b547eaa9b552b92d@stable.kernel.org> (raw)
In-Reply-To: <20250125000112.22389-1-surajjs@amazon.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 031d6f608290c847ba6378322d0986d08d1a645a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Suraj Jitindar Singh<surajjs@amazon.com>
Commit author: Konstantin Komarov<almaz.alexandrovich@paragon-software.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 550ef40fa636)
6.1.y | Present (different SHA1: d1ac7e262030)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 031d6f608290c ! 1: 4e423d945bbe7 fs/ntfs3: Additional check in ntfs_file_release
@@ Metadata
## Commit message ##
fs/ntfs3: Additional check in ntfs_file_release
+ commit 031d6f608290c847ba6378322d0986d08d1a645a upstream.
+
Reported-by: syzbot+8c652f14a0fde76ff11d@syzkaller.appspotmail.com
Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
+ Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ Signed-off-by: Suraj Jitindar Singh <surajjs@amazon.com>
## fs/ntfs3/file.c ##
@@ fs/ntfs3/file.c: static int ntfs_file_release(struct inode *inode, struct file *file)
+ int err = 0;
+
/* If we are last writer on the inode, drop the block reservation. */
- if (sbi->options->prealloc &&
- ((file->f_mode & FMODE_WRITE) &&
-- atomic_read(&inode->i_writecount) == 1)) {
+- if (sbi->options->prealloc && ((file->f_mode & FMODE_WRITE) &&
+- atomic_read(&inode->i_writecount) == 1)) {
++ if (sbi->options->prealloc &&
++ ((file->f_mode & FMODE_WRITE) &&
+ atomic_read(&inode->i_writecount) == 1)
+ /*
+ * The only file when inode->i_fop = &ntfs_file_operations and
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-01-25 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:01 [PATCH 5.15.y] fs/ntfs3: Additional check in ntfs_file_release Suraj Jitindar Singh
2025-01-25 14:03 ` Sasha Levin [this message]
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=20250124202058-b547eaa9b552b92d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surajjs@amazon.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 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.