diff options
| author | ChenXiaoSong <chenxiaosong@kylinos.cn> | 2026-07-23 04:11:29 +0000 |
|---|---|---|
| committer | Namjae Jeon <linkinjeon@kernel.org> | 2026-08-17 15:00:52 +0900 |
| commit | df3e2150f3ea44256688ad1be9cbd7453fcf0ca2 (patch) | |
| tree | 0d9c6443b4fd6d15f99dce7ce8b1b041a3ca7129 /tools/perf/scripts/python/bin/export-to-postgresql-record | |
| parent | e9b33376bd07bca4175f7bcc2d6034ef250f8181 (diff) | |
smb/server: fix signing when a response uses more than one iov
Some SMB responses keep their data in another buffer. The SMB header
and the data are then in different iovs.
The old code only handled this for SMB2 READ. For other commands, it
signed only the last iov. QUERY_INFO and CHANGE_NOTIFY can also use
another iov for their data. Their SMB header was not signed, so Windows
will client rejected the response.
Find the iov that starts with the current SMB header. Sign this iov and
all iovs after it.
Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: ChenXiaoSong <chenxiaosong@kylinos.cn>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-record')
0 files changed, 0 insertions, 0 deletions