From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com> To: <torvalds@linux-foundation.org> Cc: <ntfs3@lists.linux.dev>, <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org> Subject: [GIT PULL] ntfs3: bugfixes for 5.19 Date: Fri, 3 Jun 2022 14:26:57 +0300 [thread overview] Message-ID: <c5c16f3d-c8a7-96b0-4fd6-056c4159fcef@paragon-software.com> (raw) Hi Linus, Please pull this branch containing ntfs3 code for 5.19. Fixed: - some memory leaks and panic; - fixed xfstests (tested on x86_64) generic/092 generic/099 generic/228 generic/240 generic/307 generic/444; - bugfix (memory leak) for 5.18 [1]; - some typos, dead code, etc. Most of the code was in linux-next branch for several months, but there are some patches, that were in linux-next branch only for a couple of days. Hopefully it is ok - no regression was detected in tests. Note: after first 9 commits there was merge with Linux 5.18. I'm not sure if this complicates things, so I've listed all commits too. Regards, Konstantin [1]: https://www.spinics.net/lists/ntfs3/msg01036.html ---------------------------------------------------------------- The following changes since commit 8bb7eca972ad531c9b149c0a51ab43a417385813: Linux 5.15 (Sun Oct 31 13:53:10 2021 -0700) are available in the Git repository at: https://github.com/Paragon-Software-Group/linux-ntfs3.git ntfs3_for_5.19 for you to fetch changes up to 724bbe49c5e427cb077357d72d240a649f2e4054: fs/ntfs3: provide block_invalidate_folio to fix memory leak (Mon May 30 13:36:45 2022 +0200) All commits: 724bbe49c5e4 fs/ntfs3: provide block_invalidate_folio to fix memory leak f26967b9f7a8 fs/ntfs3: Fix invalid free in log_replay < merge with 5.18 happened > 52e00ea6b26e fs/ntfs3: Update valid size if -EIOCBQUEUED 114346978cf6 fs/ntfs3: Check new size for limits 3880f2b816a7 fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space) 9186d472ee78 fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode if called from function ntfs_init_acl 3a2154b25a9f fs/ntfs3: Optimize locking in ntfs_save_wsl_perm 2d44667c306e fs/ntfs3: Update i_ctime when xattr is added 87e21c99bad7 fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions e95113ed4d42 fs/ntfs3: Keep preallocated only if option prealloc enabled e589f9b7078e fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()' ---------------------------------------------------------------- Konstantin Komarov (8) fs/ntfs3: Update valid size if -EIOCBQUEUED fs/ntfs3: Check new size for limits fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space) fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode if called from function ntfs_init_acl fs/ntfs3: Optimize locking in ntfs_save_wsl_perm fs/ntfs3: Update i_ctime when xattr is added fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions fs/ntfs3: Keep preallocated only if option prealloc enabled Mikulas Patocka (1) fs/ntfs3: provide block_invalidate_folio to fix memory leak Namjae Jeon (1) fs/ntfs3: Fix invalid free in log_replay Christophe JAILLET (1) fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()' fs/ntfs3/file.c | 12 +++++++++--- fs/ntfs3/frecord.c | 10 +++++++--- fs/ntfs3/fslog.c | 12 +++++++----- fs/ntfs3/inode.c | 9 ++++++-- fs/ntfs3/xattr.c | 136 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------- 5 files changed, 149 insertions(+), 30 deletions(-)
next reply other threads:[~2022-06-03 11:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-03 11:26 Konstantin Komarov [this message] 2022-06-04 0:06 ` pr-tracker-bot
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=c5c16f3d-c8a7-96b0-4fd6-056c4159fcef@paragon-software.com \ --to=almaz.alexandrovich@paragon-software.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=ntfs3@lists.linux.dev \ --cc=torvalds@linux-foundation.org \ --subject='Re: [GIT PULL] ntfs3: bugfixes for 5.19' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).