All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
	Tony Luck <tony.luck@intel.com>,
	linux-hardening@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pstore/ram: Convert to platform remove callback returning void
Date: Thu, 6 Apr 2023 15:50:49 -0700	[thread overview]
Message-ID: <642f4cca.170a0220.db953.9229@mx.google.com> (raw)
In-Reply-To: <ee6bcb45-765b-30b8-fa38-a634b58391db@igalia.com>

On Thu, Apr 06, 2023 at 12:57:30PM -0300, Guilherme G. Piccoli wrote:
> On 01/04/2023 09:00, Uwe Kleine-König wrote:
> > The .remove() callback for a platform driver returns an int which makes
> > many driver authors wrongly assume it's possible to do error handling by
> > returning an error code. However the value returned is (mostly) ignored
> > and this typically results in resource leaks. To improve here there is a
> > quest to make the remove callback return void. In the first step of this
> > quest all drivers are converted to .remove_new() which already returns
> > void.
> > 
> > Trivially convert this driver from always returning zero in the remove
> > callback to the void returning variant.
> > 
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> Thanks, it makes sense for me! Code-wise, it looks fine.
> 
> What would be interesting it to mention a mail thread discussing this or
> maybe the patch itself that added the .remove_new() idea
> [https://git.kernel.org/linus/5c5a7680e67b right?].
> 
> BTW, nice idea - converting all at once would be a terrible sync effort,
> I guess this way things will go smoothly.
> Feel free to add my:
> 
> Reviewed-by: Guilherme G. Piccoli <gpiccoli@igalia.com>

Thanks! Looks good to me.

Acked-by: Kees Cook <keescook@chromium.org>

Do you want to take these view some other tree, or should I take this
via my pstore tree?

-Kees

-- 
Kees Cook

  reply	other threads:[~2023-04-06 22:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01 12:00 [PATCH] pstore/ram: Convert to platform remove callback returning void Uwe Kleine-König
2023-04-06 15:57 ` Guilherme G. Piccoli
2023-04-06 22:50   ` Kees Cook [this message]
2023-04-08  8:10     ` Uwe Kleine-König
2023-05-09  8:25       ` Uwe Kleine-König
2023-05-10 21:07 ` Kees Cook
2023-05-11  6:13   ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=642f4cca.170a0220.db953.9229@mx.google.com \
    --to=keescook@chromium.org \
    --cc=gpiccoli@igalia.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-hardening@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.