Linux USB
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: 晏龙龙 <yanlonglong@kylinos.cn>
Cc: linux-usb <linux-usb@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 回复: [PATCH] usb: f_fs-aio-simple: add NULL checks for malloc calls
Date: Mon, 17 Aug 2026 08:53:04 +0200	[thread overview]
Message-ID: <2026081739-outbreak-sternum-837b@gregkh> (raw)
In-Reply-To: <5c4ol2f2xweh-5c4twhbnnih6@nsmail8.2--kylin--1>

On Mon, Aug 17, 2026 at 02:40:20PM +0800, 晏龙龙 wrote:
> It's userspace, why not just return an error and let the kernel clean up
> the memory automatically?
> Or better yet, just have a goto to jump to the end of the function where
> all of this code already lives?

That's what I wrote, not you?

Also, please don't send html email, or top-post.

confused,

greg k-h

      reply	other threads:[~2026-08-17  6:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  6:40 回复: [PATCH] usb: f_fs-aio-simple: add NULL checks for malloc calls 晏龙龙
2026-08-17  6:53 ` gregkh [this message]

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=2026081739-outbreak-sternum-837b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=yanlonglong@kylinos.cn \
    /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