From: Luis Chamberlain <mcgrof@kernel.org>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Cheng Xu <chengyou@linux.alibaba.com>,
Bart Van Assche <bvanassche@acm.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Pankaj Raghav <pankydev8@gmail.com>,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: siw_cm.c:255 siw_cep_put+0x125/0x130 kernel warning while testing blktests srp/002 v5.17-rc7
Date: Thu, 5 May 2022 05:48:20 -0700 [thread overview]
Message-ID: <YnPHlJWhlCbXdifi@bombadil.infradead.org> (raw)
In-Reply-To: <BYAPR15MB2631A0A967BF02C93BF0E45C99C29@BYAPR15MB2631.namprd15.prod.outlook.com>
On Thu, May 05, 2022 at 11:42:55AM +0000, Bernard Metzler wrote:
>
> > -----Original Message-----
> > >
> > > *poke*
> > >
> > > Would be good to get a fix merged. And if a patch is posted does this
> > > need to go to stable?
> > >
> > > Luis
> >
> > The patch has been accepted and merged to for-rc, see:
> >
> > INVALID URI REMOVED
> > 3A__lore.kernel.org_all_d528d83466c44687f3872eadcb8c184528b2e2d4.1650526
> > 554.git.chengyou-40linux.alibaba.com_T_&d=DwICaQ&c=jf_iaSHvJObTbx-
> > siA1ZOg&r=2TaYXQ0T-r8ZO1PP1alNwU_QJcRRLfmYTAgd3QCvqSc&m=gj2AyKoOM_k9fYF-
> > _XQ4HcYw_viOIwl6lDNPHqp7L1y2OiVRWvZkTFGFHSSZInor&s=P_HaXIXt9mBbCeBNBLsWe
> > RTz5hvnUGUvObzs8lowzCM&e=
> >
> > I think this patch need not be merged back to stable, because the issue
> > is not a functional problem, but only produce a WARN in dmesg.
> >
> > Thanks,
> > Cheng Xu
>
> I agree. It does not fix a memory leak or some such.
If the warning triggers on older kernels it means testing using this
driver will fail and those tests will be skipped. In this case the
test srp/002 would be skipped unless this is fixed to not trigger
a kernel warning.
Luis
next prev parent reply other threads:[~2022-05-05 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:53 Re: siw_cm.c:255 siw_cep_put+0x125/0x130 kernel warning while testing blktests srp/002 v5.17-rc7 Bernard Metzler
2022-04-21 2:02 ` Cheng Xu
2022-05-04 20:40 ` Luis Chamberlain
2022-05-05 8:38 ` Cheng Xu
2022-05-05 11:42 ` Bernard Metzler
2022-05-05 12:48 ` Luis Chamberlain [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-14 23:31 Luis Chamberlain
2022-04-18 8:29 ` Cheng Xu
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=YnPHlJWhlCbXdifi@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=BMT@zurich.ibm.com \
--cc=bvanassche@acm.org \
--cc=chengyou@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.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.