From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Meneghini <jmeneghi@redhat.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-nvme@lists.infradead.org, kbusch@kernel.org, hch@lst.de,
sagi@grimberg.me, axboe@kernel.dk,
Bryan Gurney <bgurney@redhat.com>,
james.smart@broadcom.com, njavali@marvell.com,
linux-scsi@vger.kernel.org, hare@suse.de,
linux-hardening@vger.kernel.org, kees@kernel.org,
gustavoars@kernel.org, emilne@redhat.com
Subject: Re: (subset) [PATCH v9 0/8] nvme-fc: FPIN link integrity handling
Date: Wed, 24 Sep 2025 21:43:28 -0400 [thread overview]
Message-ID: <yq1zfajqpec.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <513ae24d-fe17-4dd1-a226-4c699e94c0e3@redhat.com> (John Meneghini's message of "Tue, 23 Sep 2025 15:21:27 -0400")
John,
> We've been testing this patch and it turns out there is a significant
> bug here.
>
> This bug causes a call trace and a driver hang.
>
> I suggest you remove this from scsi-queue and let us fix it.
I am not rebasing the tree at this point. Please submit a revert with a
problem description.
Thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2025-09-25 1:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 20:07 [PATCH v9 0/8] nvme-fc: FPIN link integrity handling Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 1/9] fc_els: use 'union fc_tlv_desc' Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 2/9] nvme: add NVME_CTRL_MARGINAL flag Bryan Gurney
2025-08-18 12:07 ` Hannes Reinecke
2025-08-13 20:07 ` [PATCH v9 3/9] nvme-fc: marginal path handling Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 4/9] nvme-fc: nvme_fc_fpin_rcv() callback Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 5/9] lpfc: enable FPIN notification for NVMe Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 6/9] qla2xxx: " Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 7/9] nvme: sysfs: emit the marginal path state in show_state() Bryan Gurney
2025-08-13 20:07 ` [PATCH v9 8/9] nvme-multipath: queue-depth support for marginal paths Bryan Gurney
2025-08-18 12:08 ` Hannes Reinecke
2025-08-13 20:07 ` [PATCH v9 9/9] scsi: qla2xxx: Fix memcpy field-spanning write issue Bryan Gurney
2025-08-18 12:09 ` Hannes Reinecke
2025-08-20 2:13 ` Martin K. Petersen
2025-08-20 2:18 ` [PATCH v9 0/8] nvme-fc: FPIN link integrity handling Martin K. Petersen
2025-08-26 2:33 ` (subset) " Martin K. Petersen
2025-09-23 19:21 ` John Meneghini
2025-09-25 1:43 ` Martin K. Petersen [this message]
2025-09-25 13:07 ` [PATCH] Revert "scsi: qla2xxx: Fix memcpy() field-spanning write issue" John Meneghini
2025-09-25 13:38 ` Gustavo A. R. Silva
2025-09-25 14:18 ` John Meneghini
2025-09-25 14:30 ` Gustavo A. R. Silva
2025-09-25 17:02 ` [PATCH RFC] scsi: qla2xxx: zero default_item last in qla24xx_free_purex_item Bryan Gurney
[not found] ` <e58d743b-a999-4e00-8f2e-31707744c5bb@embeddedor.com>
2025-09-25 18:43 ` Bryan Gurney
2025-09-25 18:54 ` Gustavo A. R. Silva
2025-09-25 18:57 ` [PATCH] Revert "scsi: qla2xxx: Fix memcpy() field-spanning write issue" Gustavo A. R. Silva
2025-09-30 9:35 ` John Meneghini
2025-09-30 20:13 ` Martin K. Petersen
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=yq1zfajqpec.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=bgurney@redhat.com \
--cc=emilne@redhat.com \
--cc=gustavoars@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=njavali@marvell.com \
--cc=sagi@grimberg.me \
/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