All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] USB: serial: ch341: GFP_KERNEL in reset_resume()
Date: Tue, 13 Sep 2022 14:59:01 +0200	[thread overview]
Message-ID: <YyB+lTC2GKgL3ZAL@hovoldconsulting.com> (raw)
In-Reply-To: <20220907132040.7747-1-oneukum@suse.com>

On Wed, Sep 07, 2022 at 03:20:40PM +0200, Oliver Neukum wrote:
> All instances of reset_resume() are potential
> parts of the block IO path. Use GFP_NOIO.

Please be more verbose here. I have to think through this every time it
is brought up, and I'm not even sure it's actually an issue any more.

Furthermore, if this is indeed still a problem, then this should be
fixed in a central place using memalloc_noio_save().

> Signed-off-by: Oliver Neukum <oneukum@suse.com>
> ---
>  drivers/usb/serial/ch341.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/serial/ch341.c b/drivers/usb/serial/ch341.c
> index af01a462cc43..3d4f68d58513 100644
> --- a/drivers/usb/serial/ch341.c
> +++ b/drivers/usb/serial/ch341.c
> @@ -137,7 +137,7 @@ static int ch341_control_in(struct usb_device *dev,

And this helper is not only used in the reset path.

>  	r = usb_control_msg_recv(dev, 0, request,
>  				 USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_DIR_IN,
>  				 value, index, buf, bufsize, DEFAULT_TIMEOUT,
> -				 GFP_KERNEL);
> +				 GFP_NOIO);
>  	if (r) {
>  		dev_err(&dev->dev, "failed to receive control message: %d\n",

Johan

      reply	other threads:[~2022-09-13 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:20 [PATCH] USB: serial: ch341: GFP_KERNEL in reset_resume() Oliver Neukum
2022-09-13 12:59 ` Johan Hovold [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=YyB+lTC2GKgL3ZAL@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    /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.