All of lore.kernel.org
 help / color / mirror / Atom feed
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 Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ntfs3: changes for 6.5
Date: Fri, 7 Jul 2023 18:14:34 +0400	[thread overview]
Message-ID: <c9649ce0-98c7-71cb-73c3-8a172d6689ff@paragon-software.com> (raw)

Hi Linus,

Please pull this branch containing ntfs3 code for 6.5.

Added:
- support /proc/fs/ntfs3/<dev>/volinfo and label;
- alternative boot if primary boot is corrupted;
- small optimizations.

Fixed:
- some endian problem;
- some logic errors;
- code is refactored and reformatted.

Regards,

Konstantin

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

The following changes since commit 6995e2de6891c724bfeb2db33d7b87775f913ad1:

    Linux 6.4 (Sun Jun 25 16:29:58 2023 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 44b4494d5c5971dc8f531c8783d90a637e862880:

    fs/ntfs3: Correct mode for label entry inside /proc/fs/ntfs3/ (Fri 
Jun 30 15:23:07 2023 +0400)

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

Edward Lo (2):
   fs/ntfs3: Enhance sanity check while generating attr_list
   fs/ntfs3: Return error for inconsistent extended attributes

Jia-Ju Bai (1):
   fs: ntfs3: Fix possible null-pointer dereferences in mi_read()

Konstantin Komarov (11):
   fs/ntfs3: Correct checking while generating attr_list
   fs/ntfs3: Fix ntfs_atomic_open
   fs/ntfs3: Mark ntfs dirty when on-disk struct is corrupted
   fs/ntfs3: Alternative boot if primary boot is corrupted
   fs/ntfs3: Do not update primary boot in ntfs_init_from_boot()
   fs/ntfs3: Code formatting
   fs/ntfs3: Code refactoring
   fs/ntfs3: Add ability to format new mft records with bigger/smaller
     header
   fs/ntfs3: Fix endian problem
   fs/ntfs3: Add support /proc/fs/ntfs3/<dev>/volinfo and
     /proc/fs/ntfs3/<dev>/label
   fs/ntfs3: Correct mode for label entry inside /proc/fs/ntfs3/

Tetsuo Handa (1):
   fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_load_attr_list()

Yangtao Li (1):
   fs/ntfs3: Use wrapper i_blocksize() in ntfs_zero_range()

Zeng Heng (1):
   ntfs: Fix panic about slab-out-of-bounds caused by ntfs_listxattr()

  fs/ntfs3/attrib.c   |   2 +-
  fs/ntfs3/attrlist.c |   7 +-
  fs/ntfs3/bitmap.c   |  10 +-
  fs/ntfs3/file.c     |   6 +-
  fs/ntfs3/frecord.c  |  58 ++++-----
  fs/ntfs3/fslog.c    |  40 +++----
  fs/ntfs3/fsntfs.c   |  99 ++++++++++++----
  fs/ntfs3/index.c    |  20 ++--
  fs/ntfs3/inode.c    |  23 ++--
  fs/ntfs3/lznt.c     |   6 +-
  fs/ntfs3/namei.c    |  31 ++---
  fs/ntfs3/ntfs.h     | 117 ++++++++++--------
  fs/ntfs3/ntfs_fs.h  |  31 ++---
  fs/ntfs3/record.c   |  14 ++-
  fs/ntfs3/run.c      |   4 +-
  fs/ntfs3/super.c    | 280 ++++++++++++++++++++++++++++++++++++++------
  fs/ntfs3/xattr.c    |  20 ++--
  17 files changed, 531 insertions(+), 237 deletions(-)


                 reply	other threads:[~2023-07-07 14:14 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=c9649ce0-98c7-71cb-73c3-8a172d6689ff@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.