From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, henrique.carvalho@suse.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] smb: client: support kvec iterators in async read path
Date: Sun, 13 Jul 2025 09:30:07 -0400 [thread overview]
Message-ID: <20250712210459-b714759afc0353ff@stable.kernel.org> (raw)
In-Reply-To: <20250710165040.3525304-1-henrique.carvalho@suse.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: 3ee1a1fc39819906f04d6c62c180e760cd3a689d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Henrique Carvalho<henrique.carvalho@suse.com>
Commit author: David Howells<dhowells@redhat.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
Found fixes commits:
92941c7f2c95 smb: fix bytes written value in /proc/fs/cifs/Stats
bb57c81e97e0 cifs: Fix rmdir failure due to ongoing I/O on deleted file
307f77e7f585 cifs: Fix reversion of the iter in cifs_readv_receive().
a68c74865f51 cifs: Fix SMB1 readv/writev callback in the same way as SMB2/3
517b58c1f924 cifs: Fix zero_point init on inode initialisation
a07d38afd152 cifs: Fix missing fscache invalidation
61ea6b3a3104 cifs: Fix setting of zero_point after DIO write
de40579b9038 cifs: Fix server re-repick on subrequest retry
ce5291e56081 cifs: Defer read completion
a88d60903696 cifs: Don't advance the I/O iterator before terminating subrequest
8a1607233566 cifs: Fix smb3_insert_range() to move the zero_point
a395726cf823 cifs: fix data corruption in read after invalidate
edfc6481faf8 smb3: fix perf regression with cached writes with netfs conversion
14b1cd25346b cifs: Fix locking in cifs_strict_readv()
Note: The patch differs from the upstream commit:
---
1: 3ee1a1fc39819 < -: ------------- cifs: Cut over to using netfslib
-: ------------- > 1: f5c5a2c4149fb smb: client: support kvec iterators in async read path
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-07-13 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 16:50 [PATCH 6.6.y] smb: client: support kvec iterators in async read path Henrique Carvalho
2025-07-11 9:01 ` David Howells
2025-07-11 15:59 ` Henrique Carvalho
2025-11-06 14:02 ` Bharath SM
2025-11-21 10:02 ` Greg KH
2025-11-21 10:31 ` Bharath SM
2025-11-27 13:30 ` Greg KH
2025-11-27 14:18 ` Bharath SM
2025-07-13 13:30 ` Sasha Levin [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=20250712210459-b714759afc0353ff@stable.kernel.org \
--to=sashal@kernel.org \
--cc=henrique.carvalho@suse.com \
--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.