[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025063022-chump-pointless-6580@gregkh>
Date: Mon, 30 Jun 2025 19:16:38 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Abdun Nihaal <abdun.nihaal@...il.com>
Cc: andy@...nel.org, dan.carpenter@...aro.org, lorenzo.stoakes@...cle.com,
tzimmermann@...e.de, riyandhiman14@...il.com, willy@...radead.org,
notro@...nnes.org, thomas.petazzoni@...e-electrons.com,
dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
Andy Shevchenko <andriy.shevchenko@...el.com>
Subject: Re: [PATCH v3 2/2] staging: fbtft: cleanup error handling in
fbtft_framebuffer_alloc()
On Sun, Jun 29, 2025 at 08:10:11PM +0530, Abdun Nihaal wrote:
> The error handling in fbtft_framebuffer_alloc() mixes managed allocation
> and plain allocation, and performs error handling in an order different
> from the order in fbtft_framebuffer_release().
>
> Fix them by moving vmem allocation closer to where it is used, and using
> plain kzalloc() for txbuf allocation.
>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@...el.com>
> Suggested-by: Dan Carpenter <dan.carpenter@...aro.org>
> Signed-off-by: Abdun Nihaal <abdun.nihaal@...il.com>
> ---
> v2->v3:
> - Remove the if check before kfree of txbuf.buf, because it is zero
> initialized on allocation, and kfree is NULL aware.
This patch does not apply to my tree, can you rebase and resend?
thanks,
greg k-h
Powered by blists - more mailing lists