On Tue, Apr 23, 2024 at 11:33:15AM +0100, Simon Horman wrote:
> On Wed, Apr 17, 2024 at 10:43:11AM +0300, Roi Dayan wrote:
> >
> >
> > On 16/04/2024 18:48, Simon Horman wrote:
> > > On Tue, Apr 16, 2024 at 04:21:48PM +0300, Roi Dayan via dev wrote:
> > >> VLOG_WARN_BUF() is allocating memory for
On Wed, Apr 17, 2024 at 10:43:11AM +0300, Roi Dayan wrote:
>
>
> On 16/04/2024 18:48, Simon Horman wrote:
> > On Tue, Apr 16, 2024 at 04:21:48PM +0300, Roi Dayan via dev wrote:
> >> VLOG_WARN_BUF() is allocating memory for the error string and should
> >> e used if the configuration cannot contin
On 16/04/2024 18:48, Simon Horman wrote:
> On Tue, Apr 16, 2024 at 04:21:48PM +0300, Roi Dayan via dev wrote:
>> VLOG_WARN_BUF() is allocating memory for the error string and should
>> e used if the configuration cannot continue and error is being returned
>> so the caller has indication of rele
On Tue, Apr 16, 2024 at 04:21:48PM +0300, Roi Dayan via dev wrote:
> VLOG_WARN_BUF() is allocating memory for the error string and should
> e used if the configuration cannot continue and error is being returned
> so the caller has indication of releasing the pointer.
> Change to VLOG_WARN() to kee
VLOG_WARN_BUF() is allocating memory for the error string and should
e used if the configuration cannot continue and error is being returned
so the caller has indication of releasing the pointer.
Change to VLOG_WARN() to keep the logic that error is not being
returned.
Fixes: f4336f504b17 ("netdev
