All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Komarovc <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 6.6
Date: Thu, 19 Oct 2023 09:37:33 +0300	[thread overview]
Message-ID: <e7b035ea-320e-465f-966f-0c370f9848be@paragon-software.com> (raw)

Hi Linus,

Please pull this branch containing ntfs3 code for 6.6.

Fixed:
- memory leak;
- some logic errors, NULL dereferences;
- some code was refactored.

Added:
- more checks.

All changed code was in linux-next branch for several weeks.

Regards,

Konstantin

----------------------------------------------------------------

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

    Linux 6.6-rc1 (Sun Sep 10 16:28:41 2023 -0700)

are available in the Git repository at:

    https://github.com/Paragon-Software-Group/linux-ntfs3.git ntfs3_for_6.6

for you to fetch changes up to e4494770a5cad3c9d1d2a65ed15d07656c0d9b82:

    fs/ntfs3: Avoid possible memory leak (Mon Sep 25 12:48:07 2023 +0800)

----------------------------------------------------------------

Gabriel Marcano (1):
   fs/ntfs3: Fix directory element type detection

Konstantin Komarov (14):
   fs/ntfs3: Add ckeck in ni_update_parent()
   fs/ntfs3: Write immediately updated ntfs state
   fs/ntfs3: Use kvmalloc instead of kmalloc(... __GFP_NOWARN)
   fs/ntfs3: Add more attributes checks in mi_enum_attr()
   fs/ntfs3: fix deadlock in mark_as_free_ex
   fs/ntfs3: Fix shift-out-of-bounds in ntfs_fill_super
   fs/ntfs3: Use inode_set_ctime_to_ts instead of inode_set_ctime
   fs/ntfs3: Allow repeated call to ntfs3_put_sbi
   fs/ntfs3: Fix alternative boot searching
   fs/ntfs3: Refactoring and comments
   fs/ntfs3: Add more info into /proc/fs/ntfs3/<dev>/volinfo
   fs/ntfs3: Do not allow to change label if volume is read-only
   fs/ntfs3: Fix possible NULL-ptr-deref in ni_readpage_cmpr()
   fs/ntfs3: Fix NULL pointer dereference on error in
     attr_allocate_frame()

Pavel Skripkin (1):
   fs/ntfs3: Fix OOB read in ntfs_init_from_boot

Su Hui (1):
   fs/ntfs3: Avoid possible memory leak

Zeng Heng (1):
   fs/ntfs3: fix panic about slab-out-of-bounds caused by ntfs_list_ea()

Ziqi Zhao (1):
   fs/ntfs3: Fix possible null-pointer dereference in hdr_find_e()

  fs/ntfs3/attrib.c   |  12 +++--
  fs/ntfs3/attrlist.c |  15 ++++++-
  fs/ntfs3/bitmap.c   |   4 +-
  fs/ntfs3/dir.c      |   6 ++-
  fs/ntfs3/file.c     |   4 +-
  fs/ntfs3/frecord.c  |   8 +++-
  fs/ntfs3/fslog.c    |   6 ++-
  fs/ntfs3/fsntfs.c   |  19 ++++----
  fs/ntfs3/index.c    |   3 ++
  fs/ntfs3/inode.c    |   5 ++-
  fs/ntfs3/namei.c    |   6 +--
  fs/ntfs3/ntfs.h     |   2 +-
  fs/ntfs3/ntfs_fs.h  |   4 +-
  fs/ntfs3/record.c   |  74 ++++++++++++++++++++++++-------
  fs/ntfs3/super.c    | 104 +++++++++++++++++++++++++++++++-------------
  fs/ntfs3/xattr.c    |   7 ++-
  16 files changed, 197 insertions(+), 82 deletions(-)



                 reply	other threads:[~2023-10-19  6:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e7b035ea-320e-465f-966f-0c370f9848be@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 \
    /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.