From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Borislav Petkov <bp@alien8.de>,
Julian Wollrath <jwollrath@web.de>,
linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops with v6.6-rc6+
Date: Sun, 22 Oct 2023 13:06:25 -0400 [thread overview]
Message-ID: <b4ebea2eeb63aaa7ba0877cee0c9ca966af9eae0.camel@HansenPartnership.com> (raw)
In-Reply-To: <20231022161847.GAZTVLZ74T8B79v87p@fat_crate.local>
On Sun, 2023-10-22 at 18:18 +0200, Borislav Petkov wrote:
> + linux-scsi
>
> On Sun, Oct 22, 2023 at 05:27:00PM +0200, Julian Wollrath wrote:
> > Dear maintainers,
> >
> > on v6.6-rc6+ (git commit hash 1acfd2bd3f0d) I got the following
> > oops:
How to reproduce would be helpful. Was this a cat of /proc/scsi/scsi?
Regards,
James
next prev parent reply other threads:[~2023-10-22 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 15:27 Oops with v6.6-rc6+ Julian Wollrath
2023-10-22 16:18 ` Borislav Petkov
2023-10-22 17:06 ` James Bottomley [this message]
2023-10-22 17:22 ` Borislav Petkov
2023-10-22 18:18 ` Julian Wollrath
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=b4ebea2eeb63aaa7ba0877cee0c9ca966af9eae0.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bp@alien8.de \
--cc=jwollrath@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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