mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Mihai Brodschi <m.brodschi@gmail.com>, <ntfs3@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] ntfs3: Allocate iomap inline_data using alloc_page
Date: Thu, 28 May 2026 15:46:52 +0200	[thread overview]
Message-ID: <e3845163-90e6-4565-bf12-5b499ae4cbfa@paragon-software.com> (raw)
In-Reply-To: <d3fd7e93-748c-4e51-ace9-a0f0a8346045@gmail.com>

On 5/11/26 19:19, Mihai Brodschi wrote:

> [You don't often get email from m.brodschi@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> This fixes a BUG reported in iomap_write_end_inline:
> iomap_inline_data_valid checks that the inline_data fits within
> a page. If the inline_data is allocated with kmemdup there's no
> guarantee that it's page-aligned, so the check sometimes fails.
> Allocate it with alloc_page to ensure it's page-aligned.
>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221446
> Signed-off-by: Mihai Brodschi <m.brodschi@gmail.com>
> Fixes: 099ef9a ("fs/ntfs3: implement iomap-based file operations")
> ---
> V3: fix variable declaration
> V2: fix mail formatting
>
>   fs/ntfs3/attrib.c | 10 +++++++---
>   fs/ntfs3/inode.c  |  4 ++--
>   2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ntfs3/attrib.c b/fs/ntfs3/attrib.c
> index e61c5bf7e27e..ff0bf4575948 100644
> --- a/fs/ntfs3/attrib.c
> +++ b/fs/ntfs3/attrib.c
> @@ -1004,6 +1004,7 @@ int attr_data_get_block_locked(struct ntfs_inode *ni, CLST vcn, CLST clen,
>          struct ATTRIB *attr, *attr_b;
>          struct ATTR_LIST_ENTRY *le, *le_b;
>          struct mft_inode *mi, *mi_b;
> +       struct page *page;
>          CLST hint, svcn, to_alloc, evcn1, next_svcn, asize, end, vcn0;
>          CLST alloc, evcn;
>          unsigned fr;
> @@ -1042,10 +1043,13 @@ int attr_data_get_block_locked(struct ntfs_inode *ni, CLST vcn, CLST clen,
>                  *lcn = RESIDENT_LCN;
>                  *len = data_size;
>                  if (res && data_size) {
> -                       *res = kmemdup(resident_data(attr_b), data_size,
> -                                      GFP_KERNEL);
> -                       if (!*res)
> +                       page = alloc_page(GFP_KERNEL);
> +                       if (!page) {
>                                  err = -ENOMEM;
> +                       } else {
> +                               *res = page_address(page);
> +                               memcpy(*res, resident_data(attr_b), data_size);
> +                       }
>                  }
>                  goto out;
>          }
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index 42af1abe17f8..031f85fd53d4 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -801,7 +801,7 @@ static int ntfs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
>
>          if (lcn == RESIDENT_LCN) {
>                  if (offset >= clen) {
> -                       kfree(res);
> +                       __free_page(virt_to_page(res));
>                          if (flags & IOMAP_REPORT) {
>                                  /* special code for report. */
>                                  return -ENOENT;
> @@ -921,7 +921,7 @@ static int ntfs_iomap_end(struct inode *inode, loff_t pos, loff_t length,
>
>   out:
>          if (iomap->type == IOMAP_INLINE) {
> -               kfree(iomap->private);
> +               __free_page(virt_to_page(iomap->private));
>                  iomap->private = NULL;
>          }
>
> --
> 2.53.0
>
Hello,

Your patch was applied, thank you.

Regards,
Konstantin


      reply	other threads:[~2026-05-28 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 17:19 Mihai Brodschi
2026-05-28 13:46 ` Konstantin Komarov [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=e3845163-90e6-4565-bf12-5b499ae4cbfa@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.brodschi@gmail.com \
    --cc=ntfs3@lists.linux.dev \
    /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®