From: Adrian Hunter <adrian.hunter@intel.com>
To: Avri Altman <Avri.Altman@wdc.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] mmc: core: Use GFP_NOIO in ACMD22
Date: Mon, 21 Oct 2024 17:33:35 +0300 [thread overview]
Message-ID: <0ead8466-a068-4e1f-93aa-47dc269b5b62@intel.com> (raw)
In-Reply-To: <DM6PR04MB6575EAADE9A5C775C0837361FC432@DM6PR04MB6575.namprd04.prod.outlook.com>
On 21/10/24 15:24, Avri Altman wrote:
>>
>> On 18/10/24 08:29, Avri Altman wrote:
>>> While reviewing the SDUC series, Adrian made a comment concerning the
>>> memory allocation code in mmc_sd_num_wr_blocks() - see [1].
>>> Prevent memory allocations from triggering I/O operations while ACMD22
>>> is in progress.
>>>
>>> [1] https://www.spinics.net/lists/linux-mmc/msg82199.html
>>>
>>> Suggested-by: Adrian Hunter <adrian.hunter@intel.com>
>>> Signed-off-by: Avri Altman <avri.altman@wdc.com>
>>> Cc: stable@vger.kernel.org
>>
>> Some checkpatch warnings:
>>
>> WARNING: Use lore.kernel.org archive links when possible - see
>> https://lore.kernel.org/lists.html
>> #12:
>> [1] https://www.spinics.net/lists/linux-mmc/msg82199.html
> Done.
>
>>
>> WARNING: The commit message has 'stable@', perhaps it also needs a
>> 'Fixes:' tag?
> I tried to look for the patch that introduced mmc_sd_num_wr_blocks but couldn't find it in Ulf's tree.
Seems like the following introduced the kmalloc()
commit 051913dada046ac948eb6f48c0717fc25de2a917
Author: Ben Dooks <ben@simtec.co.uk>
Date: Mon Jun 8 23:33:57 2009 +0100
mmc_block: do not DMA to stack
>
> Thanks,
> Avri
>>
>> total: 0 errors, 2 warnings, 17 lines checked
>>
>> Otherwise:
>>
>> Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
>>
>>>
>>> ---
>>> Changes since v1:
>>> - Move memalloc_noio_restore around (Adrian)
>>> ---
>>> drivers/mmc/core/block.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c index
>>> 04f3165cf9ae..a813fd7f39cc 100644
>>> --- a/drivers/mmc/core/block.c
>>> +++ b/drivers/mmc/core/block.c
>>> @@ -995,6 +995,8 @@ static int mmc_sd_num_wr_blocks(struct mmc_card
>> *card, u32 *written_blocks)
>>> u32 result;
>>> __be32 *blocks;
>>> u8 resp_sz = mmc_card_ult_capacity(card) ? 8 : 4;
>>> + unsigned int noio_flag;
>>> +
>>> struct mmc_request mrq = {};
>>> struct mmc_command cmd = {};
>>> struct mmc_data data = {};
>>> @@ -1018,7 +1020,9 @@ static int mmc_sd_num_wr_blocks(struct
>> mmc_card *card, u32 *written_blocks)
>>> mrq.cmd = &cmd;
>>> mrq.data = &data;
>>>
>>> + noio_flag = memalloc_noio_save();
>>> blocks = kmalloc(resp_sz, GFP_KERNEL);
>>> + memalloc_noio_restore(noio_flag);
>>> if (!blocks)
>>> return -ENOMEM;
>>>
>
next prev parent reply other threads:[~2024-10-21 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 5:29 [PATCH v2] mmc: core: Use GFP_NOIO in ACMD22 Avri Altman
2024-10-21 10:47 ` Adrian Hunter
2024-10-21 12:24 ` Avri Altman
2024-10-21 14:33 ` Adrian Hunter [this message]
2024-10-21 15:26 ` Avri Altman
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=0ead8466-a068-4e1f-93aa-47dc269b5b62@intel.com \
--to=adrian.hunter@intel.com \
--cc=Avri.Altman@wdc.com \
--cc=linux-mmc@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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