diff options
author | Pali Rohár <pali@kernel.org> | 2024-09-12 14:05:44 +0200 |
---|---|---|
committer | Steve French <stfrench@microsoft.com> | 2024-09-15 10:42:45 -0500 |
commit | bb68327053a24734d5a146620f8a29219361dd3e (patch) | |
tree | fa8516c01626f7acd460fdd7bbae38322f8238b7 /kernel/kallsyms.c | |
parent | cf2ce67345d6a1af0853d8a7aef9ab8e6ea597d5 (diff) |
cifs: Put explicit zero byte into SFU block/char types
SFU types IntxCHR and IntxBLK are 8 bytes with zero as last byte. Make it
explicit in memcpy and memset calls, so the zero byte is visible in the
code (and not hidden as string trailing nul byte).
It is important for reader to show the last byte for block and char types
because it differs from the last byte of symlink type (which has it 0x01).
Also it is important to show that the type is not nul-term string, but
rather 8 bytes (with some printable bytes).
Signed-off-by: Pali Rohár <pali@kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'kernel/kallsyms.c')
0 files changed, 0 insertions, 0 deletions