All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: Paul Aurich <paul@darkrain42.org>,
	linux-cifs@vger.kernel.org, stable@vger.kernel.org,
	Namjae Jeon <linkinjeon@kernel.org>
Cc: Henrique Carvalho <henrique.carvalho@suse.com>,
	Sasha Levin <sashal@kernel.org>,
	regressions@lists.linux.dev
Subject: Re: [REGRESSION] smb: client: batch SRV_COPYCHUNK entries to cut round trips - 6.12.y EIO above 12 MiB with SMB3 encryption
Date: Thu, 15 Oct 2026 16:54:29 -0300	[thread overview]
Message-ID: <441cd931c56cb539eb099bf6d976cc59@manguebit.org> (raw)
In-Reply-To: <atEn9dyqsyI3SNaP@redcloak.home.arpa>

Thanks for the report.

Paul Aurich <paul@darkrain42.org> writes:

> In stable 6.12.y releases, a copy_file_range request exceeding 12 MiB on an
> encrypted SMB3 mount fails with EIO and a WARN_ON_ONCE() splat in
> SMB2_ioctl_init:
>
>      # cp /mnt/otters/13mib.bin /mnt/otters/output.bin
>      cp: error copying '/mnt/otters/13mib.bin' to '/mnt/otters/output.bin':
>      Input/output error
>
> Works in 6.12.110.  Fails in 6.12.111 through 6.12.113 (latest).  Via
> bisection, introduced by 8d103b285359 ("smb: client: batch SRV_COPYCHUNK
> entries to cut round trips").

Does it work if you backport the other 3 missing commits?

  reply	other threads:[~2026-10-15 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 19:22 [REGRESSION] smb: client: batch SRV_COPYCHUNK entries to cut round trips - 6.12.y EIO above 12 MiB with SMB3 encryption Paul Aurich
2026-10-15 19:54 ` Paulo Alcantara [this message]
2026-10-15 21:28   ` Paul Aurich
2026-10-16 14:08     ` Paulo Alcantara
2026-10-16 14:51       ` Greg Kroah-Hartman

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=441cd931c56cb539eb099bf6d976cc59@manguebit.org \
    --to=pc@manguebit.org \
    --cc=henrique.carvalho@suse.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=paul@darkrain42.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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.