From: Kevin Wolf <kwolf@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-block@nongnu.org, hreitz@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, qemu-devel@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [PATCH for-10.0] scsi-disk: Apply error policy for host_status errors again
Date: Tue, 13 May 2025 13:53:15 +0200 [thread overview]
Message-ID: <aCMyqz9diQHcPR5R@redhat.com> (raw)
In-Reply-To: <a2ec9fe4-c25f-4610-a1da-fe87817fe9f2@tls.msk.ru>
Am 10.04.2025 um 15:33 hat Michael Tokarev geschrieben:
> 10.04.2025 16:14, Kevin Wolf wrote:
> > Am 10.04.2025 um 14:37 hat Michael Tokarev geschrieben:
> ...>> Does it make sense to apply this one for older stable qemu series?
> > > In particular, in 8.2, we lack cfe0880835cd3
> > > "scsi-disk: Use positive return value for status in dma_readv/writev",
> > > which seems to be relevant here. Or should I pick up cfe0880835cd3 too,
> > > maybe together with 8a0495624f (a no-op, just to make this patch to apply
> > > cleanly) and probably 9da6bd39f924?
> >
> > Yes, I think it makes sense to pick all of them up (and 622a7016 in the
> > middle, too), they were part of one series:
> >
> > https://patchew.org/QEMU/20240731123207.27636-1-kwolf@redhat.com/
> >
> > And this patch builds on top of that series, so rebasing it correctly
> > might not be trivial without the previous series.
>
> A (most likely small) issue here: 622a70161a "scsi-block: Don't skip
> callback for sgio error status/driver_status" is on top of an earlier
> commit, 1404226804 "scsi: don't lock AioContext in I/O code path",
> but does not actually *require* it, since it removes whole code block
> where a locking has been removed earlier by 1404226804.
Right, a backport should just remove the locking with it. That seems to
be a trivial conflict resolution.
> Also the next comment commit, 8a0495624f "scsi-disk: Add warning comments
> that host_status errors take a shortcut", clashes with e7fc3c4a8cc "scsi:
> remove outdated AioContext lock comment".
It's only comments anyway, but the correct conflict resolution here is
to keep both comments.
> This seems a bit too fragile for 8.2, don't you think? And I haven't even
> tried to check 7.2 yet :)
Both of the merge conflicts you mentioned above don't really seem like
problems to me. Did you find any semantic merge conflicts? That's when I
would start to be concerned about fragility.
> https://gitlab.com/mjt0k/qemu/-/tree/staging-8.2 for the current result
> (not yet tested) - I dislike my comment handling at scsi_dma_complete().
Seems you already resolved the conflicts the same was as I suggested
above.
Kevin
next prev parent reply other threads:[~2025-05-13 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 15:59 [PATCH for-10.0] scsi-disk: Apply error policy for host_status errors again Kevin Wolf
2025-04-07 18:19 ` Stefan Hajnoczi
2025-04-08 12:21 ` Hanna Czenczek
2025-04-10 12:37 ` Michael Tokarev
2025-04-10 13:14 ` Kevin Wolf
2025-04-10 13:33 ` Michael Tokarev
2025-05-13 11:53 ` Kevin Wolf [this message]
2025-04-10 14:25 ` Paolo Bonzini
2025-04-10 15:28 ` Paolo Bonzini
2025-04-11 10:18 ` Kevin Wolf
2025-04-11 10:20 ` Paolo Bonzini
2025-05-12 9:23 ` Michael Tokarev
2025-05-13 11:42 ` Kevin Wolf
2025-05-13 11:46 ` Michael Tokarev
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=aCMyqz9diQHcPR5R@redhat.com \
--to=kwolf@redhat.com \
--cc=hreitz@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.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.