RE: [PATCH v2 0/4] makedumpfile: harden parsing of old prink buffer

-Original Message- > On Wed, Mar 16, 2022 at 9:17 AM David Wysochanski wrote: > > > > On Mon, Mar 14, 2022 at 12:04 PM Philipp Rudo wrote: > > > > > > Hi, > > > > > > dumping the dmesg can cause an endless loop for the old prink mechanism (> > > > v3.5.0 and < v5.10.0) when the log_buf

Re: [PATCH v2 0/4] makedumpfile: harden parsing of old prink buffer

On Wed, Mar 16, 2022 at 9:17 AM David Wysochanski wrote: > > On Mon, Mar 14, 2022 at 12:04 PM Philipp Rudo wrote: > > > > Hi, > > > > dumping the dmesg can cause an endless loop for the old prink mechanism (> > > v3.5.0 and < v5.10.0) when the log_buf got corrupted. This series fixes > > those

Re: [PATCH v2 0/4] makedumpfile: harden parsing of old prink buffer

On Mon, Mar 14, 2022 at 12:04 PM Philipp Rudo wrote: > > Hi, > > dumping the dmesg can cause an endless loop for the old prink mechanism (> > v3.5.0 and < v5.10.0) when the log_buf got corrupted. This series fixes those > cases by adding a cycle detection. The cycle detection is implemented in a

[PATCH v2 0/4] makedumpfile: harden parsing of old prink buffer

Hi, dumping the dmesg can cause an endless loop for the old prink mechanism (> v3.5.0 and < v5.10.0) when the log_buf got corrupted. This series fixes those cases by adding a cycle detection. The cycle detection is implemented in a generic way so that it can be reused in other parts of