Re: [PATCH v2] wimax/i2400m: fix a memory leak bug

2019-08-18 Thread Perez-Gonzalez, Inaky
This driver should be orphaned. While I can’t certainly say nobody is using it, the HW has not been sold for years and it hasn’t been brought to current LK standards. If your assesment is the code shall not be used, it’s then another argument towards disconnecting it. > On Aug 18, 2019, at

Re: [PATCH v2] wimax/i2400m: fix a memory leak bug

2019-08-18 Thread David Miller
From: Wenwen Wang Date: Thu, 15 Aug 2019 15:29:51 -0500 > In i2400m_barker_db_init(), 'options_orig' is allocated through kstrdup() > to hold the original command line options. Then, the options are parsed. > However, if an error occurs during the parsing process, 'options_orig' is > not

[PATCH v2] wimax/i2400m: fix a memory leak bug

2019-08-15 Thread Wenwen Wang
In i2400m_barker_db_init(), 'options_orig' is allocated through kstrdup() to hold the original command line options. Then, the options are parsed. However, if an error occurs during the parsing process, 'options_orig' is not deallocated, leading to a memory leak bug. To fix this issue, free