bpf: Use strncpy_from_unsafe_strict() in bpf_seq_printf() helper
In bpf_seq_printf() helper, when user specified a "%s" in the format string, strncpy_from_unsafe() is used to read the actual string to a buffer. The string could be a format string or a string in the kernel data structure. It is really unlikely that the string will reside in the user memory. This is different from Commitb2a5212fb6
("bpf: Restrict bpf_trace_printk()'s %s usage and add %pks, %pus specifier") which still used strncpy_from_unsafe() for "%s" to preserve the old behavior. If in the future, bpf_seq_printf() indeed needs to read user memory, we can implement "%pus" format string. Based on discussion in [1], if the intent is to read kernel memory, strncpy_from_unsafe_strict() should be used. So this patch changed to use strncpy_from_unsafe_strict(). [1]: https://lore.kernel.org/bpf/20200521152301.2587579-1-hch@lst.de/T/ Fixes:492e639f0c
("bpf: Add bpf_seq_printf and bpf_seq_write helpers") Signed-off-by: Yonghong Song <yhs@fb.com> Signed-off-by: Alexei Starovoitov <ast@kernel.org> Acked-by: Song Liu <songliubraving@fb.com> Cc: Christoph Hellwig <hch@lst.de> Link: https://lore.kernel.org/bpf/20200529004810.3352219-1-yhs@fb.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
This commit is contained in:
parent
c3c16f2ea6
commit
b36e62eb85
|
@ -585,9 +585,9 @@ BPF_CALL_5(bpf_seq_printf, struct seq_file *, m, char *, fmt, u32, fmt_size,
|
||||||
goto out;
|
goto out;
|
||||||
}
|
}
|
||||||
|
|
||||||
err = strncpy_from_unsafe(bufs->buf[memcpy_cnt],
|
err = strncpy_from_unsafe_strict(bufs->buf[memcpy_cnt],
|
||||||
(void *) (long) args[fmt_cnt],
|
(void *) (long) args[fmt_cnt],
|
||||||
MAX_SEQ_PRINTF_STR_LEN);
|
MAX_SEQ_PRINTF_STR_LEN);
|
||||||
if (err < 0)
|
if (err < 0)
|
||||||
bufs->buf[memcpy_cnt][0] = '\0';
|
bufs->buf[memcpy_cnt][0] = '\0';
|
||||||
params[fmt_cnt] = (u64)(long)bufs->buf[memcpy_cnt];
|
params[fmt_cnt] = (u64)(long)bufs->buf[memcpy_cnt];
|
||||||
|
|
Loading…
Reference in New Issue