Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Cyril Brulebois <kibi@debian.org>
To: James Bottomley <jejb@linux.ibm.com>
Cc: regressions@lists.linux.dev, stable@vger.kernel.org,
	Mike Christie <michael.christie@oracle.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Sasha Levin <sashal@kernel.org>,
	gregkh@linuxfoundation.org, Bart Van Assche <bvanassche@acm.org>,
	Christoph Hellwig <hch@lst.de>,
	John Garry <john.g.garry@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Diederik de Haas <didi.debian@cknow.org>,
	Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [REGRESSION] Loss of some SMART information in v6.1.81
Date: Thu, 11 Apr 2024 06:33:27 +0200	[thread overview]
Message-ID: <20240411043327.m5unlpweoslnzzce@mraw.org> (raw)
In-Reply-To: <0655cea93e52928d3e4a12b4fe2d2a4375492ed3.camel@linux.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 581 bytes --]

James Bottomley <jejb@linux.ibm.com> (2024-04-10):
> This is a different manifestation of the same bug in stable that was
> introduced by a backport of scsi_execute_cmd.  The proposed fix for the
> domain validation problem here will also sort out this problem:
> 
> https://lore.kernel.org/linux-scsi/yq1frvvpymp.fsf@ca-mkp.ca.oracle.com/

Thanks for the pointer! I've just confirmed this, and I'll follow up
there.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-04-11  4:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 19:32 [REGRESSION] Loss of some SMART information in v6.1.81 Cyril Brulebois
2024-04-10 19:36 ` James Bottomley
2024-04-11  4:33   ` Cyril Brulebois [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=20240411043327.m5unlpweoslnzzce@mraw.org \
    --to=kibi@debian.org \
    --cc=bvanassche@acm.org \
    --cc=carnil@debian.org \
    --cc=didi.debian@cknow.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michael.christie@oracle.com \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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