-
Notifications
You must be signed in to change notification settings - Fork 148
bpf: Don't use %pK through printk #9443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Upstream branch: fa47913 |
2a0e5cd
to
2562e0e
Compare
Upstream branch: 9e293d4 |
3d93f2c
to
9ab4fc6
Compare
2562e0e
to
5583eb6
Compare
Upstream branch: 3e2b799 |
9ab4fc6
to
6128680
Compare
5583eb6
to
601ea2d
Compare
Upstream branch: c93c59b |
6128680
to
2a14964
Compare
601ea2d
to
7390c2c
Compare
In the past %pK was preferable to %p as it would not leak raw pointer values into the kernel log. Since commit ad67b74 ("printk: hash addresses printed with %p") the regular %p has been improved to avoid this issue. Furthermore, restricted pointers ("%pK") were never meant to be used through printk(). They can still unintentionally leak raw pointers or acquire sleeping locks in atomic contexts. Switch to the regular pointer formatting which is safer and easier to reason about. Signed-off-by: Thomas Weißschuh <[email protected]>
Upstream branch: bf0c2a8 |
2a14964
to
1bc0e39
Compare
7390c2c
to
3a736b5
Compare
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=990010 irrelevant now. Closing PR. |
Pull request for series with
subject: bpf: Don't use %pK through printk
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=990010