From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-scsi@vger.kernel.org,
james.bottomley@hansenpartnership.com,
Mike Christie <michael.christie@oracle.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] fcoe: fix io path allocation
Date: Mon, 17 Aug 2020 23:12:29 -0400 [thread overview]
Message-ID: <159772029325.19587.11765074400059811271.b4-ty@oracle.com> (raw)
In-Reply-To: <1596831813-9839-1-git-send-email-michael.christie@oracle.com>
On Fri, 7 Aug 2020 15:23:33 -0500, Mike Christie wrote:
> ixgbe_fcoe_ddp_setup can be called from the main IO path and is called
> with a spin_lock held, so we have to use GFP_ATOMIC allocation instead
> of GFP_KERNEL.
Applied to 5.9/scsi-fixes, thanks!
[1/1] scsi: fcoe: Fix I/O path allocation
https://git.kernel.org/mkp/scsi/c/fa39ab5184d6
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-08-18 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 20:23 [PATCH] fcoe: fix io path allocation Mike Christie
2020-08-07 22:41 ` Lee Duncan
2020-08-18 3:12 ` Martin K. Petersen [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=159772029325.19587.11765074400059811271.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michael.christie@oracle.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.