Messages in this thread | | | Subject | Re: [PATCH v3] lockdep: Allow tuning tracing capacity constants. | From | Tetsuo Handa <> | Date | Thu, 19 Nov 2020 23:57:36 +0900 |
| |
On 2020/11/19 23:30, Dmitry Vyukov wrote: > p.s. it's indeed huge, full log was 11MB, this probably won't be > chewed by syzbot.
Is "cat /proc/lockdep*" output written from userspace? Then, we could try "xz -9" + "base64" for recording.
> Peter, are these [hex numbers] needed? Could we strip them during > post-processing? At first sight they look like derivatives of the > name.
kernel/locking/lockdep.c uses %px (raw address) whereas kernel/locking/lockdep_proc.c uses %p (__ptr_to_hashval() value). I think saving these [hashed hex numbers] is unlikely useful. At least for this testing, we can strip leading 00000000 part.
| |