From: Dan Carpenter <dan.carpenter@oracle.com>
To: Peter Lafreniere <pjlafren@mtu.edu>
Cc: linux-hams@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] ax25: use GFP_KERNEL in ax25_dev_device_up()
Date: Tue, 7 Jun 2022 07:58:41 +0300 [thread overview]
Message-ID: <20220607045841.GY2146@kadam> (raw)
In-Reply-To: <20220606174012.10262-1-pjlafren@mtu.edu>
On Mon, Jun 06, 2022 at 01:40:12PM -0400, Peter Lafreniere wrote:
> ax25_dev_device_up() is only called during device setup, which is
> done in user context. In addition, ax25_dev_device_up()
> unconditionally calls ax25_register_dev_sysctl(), which already
> allocates with GFP_KERNEL.
>
> Since it is allowed to sleep in this function, here we change
> ax25_dev_device_up() to use GFP_KERNEL to reduce unnecessary
> out-of-memory errors.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Peter Lafreniere <pjlafren@mtu.edu>
> ---
I don't know if you really want to add Reported-by tags. That stuff is
just in the kbuild-bot template and it's an automated thing. Some people
add it and some don't.
It doesn't really matter either way.
> v1 -> v2:
> - Renamed patch from "ax25: use GFP_KERNEL over GFP_ATOMIC where possible"
> (Is that okay?)
No problem.
> - Removed invalid changes to ax25_rt_add()
>
> This isn't related to the patch itself, but thanks are owed to everyone
> who had to handle my mistakes in submitting this patch the first time.
> First the posting during the merge window, which I know better to do,
> then me making the stupidest error of missing a lock directly next to the
> relevant code.
It's all part of learning. No stress. There was no danger because we
caught it in review and automatically with static analysis.
regards,
dan carpenter
prev parent reply other threads:[~2022-06-07 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 17:40 [PATCH v2] ax25: use GFP_KERNEL in ax25_dev_device_up() Peter Lafreniere
2022-06-07 4:58 ` Dan Carpenter [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=20220607045841.GY2146@kadam \
--to=dan.carpenter@oracle.com \
--cc=linux-hams@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pjlafren@mtu.edu \
/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