Linus Torvalds writes: (Summary) wrote:
So I'm not convinced about this one.
It removes kernel pointers even for root, which is annoying for things like perf.
like perf.
And the only physical pointers we should print out during boot etc are things we *need*.
things we *need*.
So kptr_restrict is wrong for that, bercause either we potentially need those values for debugging ("why does my kernel not boot"), or they shouldn't be printed at all.
they shouldn't be printed at all.
And I think _that_ is the real issue.
[...]
lib: vsprintf: default kptr_restrict to the maximum value So I'm not convinced about this one.So I'm not convinced about this one.
It removes kernel pointers even for root, which is annoying for things like perf.
like perf.
And the only physical pointers we should print out during boot etc are things we *need*.
things we *need*.
So kptr_restrict is wrong for that, bercause either we potentially need those values for debugging ("why does my kernel not boot"), or they shouldn't be printed at all.
they shouldn't be printed at all.
And I think _that_ is the real issue.
