diff options
author | John Ogness <[email protected]> | 2022-04-21 23:28:41 +0206 |
---|---|---|
committer | Petr Mladek <[email protected]> | 2022-04-22 21:30:57 +0200 |
commit | 9f0844de49cf0557d5c359131004acbb179c174e (patch) | |
tree | edadcccad1fff272390ad9d4db0abf34db3793ad /lib/test_fortify/write_overflow-strlcpy-src.c | |
parent | 5341b93dea8c39d7612f7a227015d4b1d5cf30db (diff) |
printk: get caller_id/timestamp after migration disable
Currently the local CPU timestamp and caller_id for the record are
collected while migration is enabled. Since this information is
CPU-specific, it should be collected with migration disabled.
Migration is disabled immediately after collecting this information
anyway, so just move the information collection to after the
migration disabling.
Signed-off-by: John Ogness <[email protected]>
Reviewed-by: Sergey Senozhatsky <[email protected]>
Reviewed-by: Petr Mladek <[email protected]>
Signed-off-by: Petr Mladek <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions