mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: linux-kernel@vger.kernel.org, Dan Carpenter <error27@gmail.com>,
	Takashi Iwai <tiwai@suse.de>, Kees Cook <keescook@chromium.org>,
	"Luis R . Rodriguez" <mcgrof@kernel.org>,
	Brian Norris <computersforpeace@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v4 1/1] test_fimware: return -ENOMEM instead of -ENOSPC on failed memory allocation
Date: Sat, 12 Aug 2023 09:29:42 +0200	[thread overview]
Message-ID: <2023081213-reset-tadpole-fc94@gregkh> (raw)
In-Reply-To: <20230812054346.168223-1-mirsad.todorovac@alu.unizg.hr>

On Sat, Aug 12, 2023 at 07:43:47AM +0200, Mirsad Todorovac wrote:
> [ Upstream commit 7dae593cd226a0bca61201cf85ceb9335cf63682 ]
> 
> In a couple of situations like
> 
> 	name = kstrndup(buf, count, GFP_KERNEL);
> 	if (!name)
> 		return -ENOSPC;
> 
> the error is not actually "No space left on device", but "Out of memory".
> 
> It is semantically correct to return -ENOMEM in all failed kstrndup()
> and kzalloc() cases in this driver, as it is not a problem with disk
> space, but with kernel memory allocator failing allocation.
> 
> The semantically correct should be:
> 
>         name = kstrndup(buf, count, GFP_KERNEL);
>         if (!name)
>                 return -ENOMEM;
> 
> Cc: Dan Carpenter <error27@gmail.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Luis R. Rodriguez <mcgrof@kernel.org>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: stable@vger.kernel.org # 4.14
> Fixes: c92316bf8e948 ("test_firmware: add batched firmware tests")
> Fixes: 0a8adf584759c ("test: add firmware_class loader test")
> Fixes: eb910947c82f9 ("test: firmware_class: add asynchronous request trigger")
> Fixes: 061132d2b9c95 ("test_firmware: add test custom fallback trigger")
> Link: https://lore.kernel.org/all/20230606070808.9300-1-mirsad.todorovac@alu.unizg.hr/
> Signed-off-by: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
> 
> [ This is the backport of the patch to 4.19 and 4.14 branches. There are no	]
> [ semantic differences in the commit. Backport is provided for completenes sake	]
> [ so it would apply to all of the supported LTS kernels				]

This commit is already in the 4.19.291 release, does it need to be
included in there again for some reason?

thanks,

greg k-h

  reply	other threads:[~2023-08-12  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  5:43 Mirsad Todorovac
2023-08-12  7:29 ` Greg KH [this message]
2023-08-12  8:06   ` Mirsad Todorovac
2023-08-12  8:12     ` Greg KH
2023-08-12  8:53       ` Mirsad Todorovac

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=2023081213-reset-tadpole-fc94@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=computersforpeace@gmail.com \
    --cc=error27@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mirsad.todorovac@alu.unizg.hr \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®