Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paulo Alcantara <pc@manguebit.org>
Cc: Paul Aurich <paul@darkrain42.org>,
	linux-cifs@vger.kernel.org, stable@vger.kernel.org,
	Namjae Jeon <linkinjeon@kernel.org>,
	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: Fri, 16 Oct 2026 16:51:39 +0200	[thread overview]
Message-ID: <2026101633-evaluate-jurist-020f@gregkh> (raw)
In-Reply-To: <437553f9978afec2dc14363fdfedab5f@manguebit.org>

On Fri, Oct 16, 2026 at 11:08:20AM -0300, Paulo Alcantara wrote:
> Paul Aurich <paul@darkrain42.org> writes:
> 
> > On 2026-10-15 16:54:29 -0300, Paulo Alcantara wrote:
> >>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?
> >
> > Yes.  With v6.12.113 + bc925c1216f0 + 9f544d26b15b + 90f7c100d2dd, 'cp' and 
> > the Python reproducer work.  (Tested with both a 13 MiB file and a 250 MiB 
> > file)
> 
> Thanks for testing it!
> 
> Greg,
> 
> Could you please backport the following to v6.12.y
> 
> 	bc925c1216f0 ("smb: client: improve compound padding in encryption")
> 	9f544d26b15b ("smb: client: get rid of bounds check in SMB2_ioctl_init()")
> 	90f7c100d2dd ("smb: client: fix compound alignment with encryption")

Now queued up, thanks.

greg k-h

      reply	other threads:[~2026-10-16 14:51 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
2026-10-15 21:28   ` Paul Aurich
2026-10-16 14:08     ` Paulo Alcantara
2026-10-16 14:51       ` Greg Kroah-Hartman [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=2026101633-evaluate-jurist-020f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=henrique.carvalho@suse.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=paul@darkrain42.org \
    --cc=pc@manguebit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox