[Bug 2042720] Re: [SRU] segfaults with certain trace.dat files

[Dave Jones]

Patch looks good. One minor nitpick was that update-maintainer needed
running to correct the maintainer address in d/control, but I can
trivially do that. Sponsoring for lunar.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2042720

Title:
  [SRU] segfaults with certain trace.dat files

Status in kernelshark package in Ubuntu:
  Fix Released
Status in kernelshark source package in Lunar:
  Triaged
Status in kernelshark source package in Mantic:
  Fix Released
Status in kernelshark package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  KernelShark crashes when opening `trace.dat` of 'all events' and can
  be used by the user to analyze the particular trace file resulting in
  a segfault.

  [ Test Plan ]

  Grab the trace.dat file from https://bugzilla.kernel.org/show_bug.cgi?id=217429 and save it to $HOME.
  Execute kernelshark from terminal by giving the command `kernelshark` and you can see segfault.

  With the fix kernelshark will start the gui and load the trace file.

  [ Where problems could occur ]

  As the fix is in the error path and is only checking for seq.len which
  will return if its `0`. It does not change any other code and so does
  not change the behaviour so has little chance of regressing the user
  behaviour.

  
  [ Other Info ]
   
   The problem exists in 2.2.0, and has been fixed by upstream on 2.2.1. It has been updated on Ubuntu Noble and Mantic. But Lunar still has the problem.
   The diff between v2.2.0..v2.2.1 are only two bugfixes. And one of them fixes the observed segmentation fault.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernelshark/+bug/2042720/+subscriptions