From: Greg KH <gregkh@linuxfoundation.org>
To: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tomas Henzl <thenzl@redhat.com>,
Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mpi3mr: Fix duplicate device entries when scan through sysfs
Date: Wed, 13 Oct 2021 18:40:52 +0200 [thread overview]
Message-ID: <YWcMFGfAB9gFknes@kroah.com> (raw)
In-Reply-To: <CAK=zhgo4CThfpRf37J3wufSjVByErdriBFpjMeBx2EumiRhR=A@mail.gmail.com>
On Wed, Oct 13, 2021 at 09:35:39PM +0530, Sreekanth Reddy wrote:
> On Wed, Oct 13, 2021 at 1:53 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Oct 13, 2021 at 01:46:56PM +0530, Sreekanth Reddy wrote:
> > > When the user scans the devices through 'scan' sysfs using below
> > > command then the user will observe duplicate device entries
> > > in lsscsi command output.
> > > echo "- - -" > /sys/class/scsi_host/host0/scan
> > >
> > > Fix is to set the shost's max_channel to zero.
> > >
> > > Cc: stable@vger.kernel.org #v5.14.11+
> >
> > Please tag this based on a release of Linus's, or better yet, provide a
> > "Fixes:" commit so that the stable people know exactly where to backport
> > it to.
> Thanks, Shall I resend the patch with proper "Fixes:" commit ID.
Yes please.
> > As this is, we do not take patches only for stable kernels...
> This fix applies for the mainline kernel as well.
That's good, as that is the only way to get patches accepted :)
prev parent reply other threads:[~2021-10-13 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 8:16 [PATCH] mpi3mr: Fix duplicate device entries when scan through sysfs Sreekanth Reddy
2021-10-13 8:23 ` Greg KH
2021-10-13 16:05 ` Sreekanth Reddy
2021-10-13 16:40 ` Greg KH [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=YWcMFGfAB9gFknes@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=stable@vger.kernel.org \
--cc=thenzl@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.