From: Julia Lawall <julia.lawall@lip6.fr>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kbuild-all@01.org, Kurt Schwemmer <kurt.schwemmer@microsemi.com>,
Logan Gunthorpe <logang@deltatee.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Kirill Smelkov <kirr@nexedi.com>
Subject: Re: [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd)
Date: Thu, 18 Apr 2019 07:31:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904180728420.8144@hadrien> (raw)
In-Reply-To: <20190417215420.GV126710@google.com>
On Wed, 17 Apr 2019, Bjorn Helgaas wrote:
> On Sat, Apr 13, 2019 at 06:50:57PM +0200, Julia Lawall wrote:
> > Hello,
> >
> > Kirill will explain about this issue.
> >
> > julia
> >
> > ---------- Forwarded message ----------
> > Date: Sat, 13 Apr 2019 11:22:51 +0800
> > From: kbuild test robot <lkp@intel.com>
> > To: kbuild@01.org
> > Cc: Julia Lawall <julia.lawall@lip6.fr>
> > Subject: [PATCH] pci/switchtec: fix stream_open.cocci warnings
> >
> > CC: kbuild-all@01.org
> > TO: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > CC: Kurt Schwemmer <kurt.schwemmer@microsemi.com>
> > CC: Logan Gunthorpe <logang@deltatee.com>
> > CC: Bjorn Helgaas <helgaas@kernel.org>
> > CC: linux-pci@vger.kernel.org
> > CC: linux-kernel@vger.kernel.org
> >
> > From: kbuild test robot <lkp@intel.com>
> >
> > drivers/pci/switch/switchtec.c:395:1-17: ERROR: switchtec_fops: .read() can deadlock .write(); change nonseekable_open -> stream_open to fix.
> >
> > Generated by: scripts/coccinelle/api/stream_open.cocci
> >
> > Fixes: 8a29a3bae2a2 ("pci/switchtec: Don't use completion's wait queue")
> > Signed-off-by: kbuild test robot <lkp@intel.com>
>
> Based on Kirill's subsequent email saying this is already queued to
> the merge window, I assume I need to do nothing here.
>
> I think a signed-off-by from a robot, i.e., not from a real person, is
> meaningless, and I don't think I would personally accept it. It's
> certainly OK to indicate that a patch was auto-generated, but I think
> a real person still needs to take responsibility for it.
>
> Documentation/process/submitting-patches.rst says it must contain a
> real name (no pseudonyms or anonymous contributions), and I don't
> think a robot fits in the spirit of that.
>
> I see that
> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/commit/?id=8a29a3bae2a2
> (mentioned below) does have a good signed-off-by from Sebastian, but
> that's not *this* patch, so I don't know what's what.
Normally, for these robot generated patches, when I approve them, I put my
own sign off, but under the robot one, since the robot has put a From
line. In this case, I handed the problem off to Kirill, so I didn't do
that. I agree that it would be good for Kirill to sign off on it.
julia
>
> Bjorn
>
> > ---
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git linux-5.0.y-rt-rebase
> > head: 794c294ae4483c240429c25a0d18e272e92c94de
> > commit: 8a29a3bae2a2dfb0116cd8791d9700515d6e765e [154/311] pci/switchtec: Don't use completion's wait queue
> > :::::: branch date: 7 hours ago
> > :::::: commit date: 7 hours ago
> >
> > Please take the patch only if it's a positive warning. Thanks!
> >
> > switchtec.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- a/drivers/pci/switch/switchtec.c
> > +++ b/drivers/pci/switch/switchtec.c
> > @@ -392,7 +392,7 @@ static int switchtec_dev_open(struct ino
> > return PTR_ERR(stuser);
> >
> > filp->private_data = stuser;
> > - nonseekable_open(inode, filp);
> > + stream_open(inode, filp);
> >
> > dev_dbg(&stdev->dev, "%s: %p\n", __func__, stuser);
> >
>
next prev parent reply other threads:[~2019-04-18 5:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 16:50 [PATCH] pci/switchtec: fix stream_open.cocci warnings (fwd) Julia Lawall
2019-04-13 16:56 ` Logan Gunthorpe
2019-04-13 17:01 ` Kirill Smelkov
2019-04-15 14:38 ` Sebastian Andrzej Siewior
2019-04-15 14:55 ` Kirill Smelkov
2019-04-15 15:20 ` Sebastian Andrzej Siewior
2019-04-15 15:41 ` Kirill Smelkov
2019-04-17 21:54 ` Bjorn Helgaas
2019-04-18 5:31 ` Julia Lawall [this message]
2019-04-18 10:38 ` Kirill Smelkov
2019-04-18 12:37 ` Bjorn Helgaas
2019-04-18 14:42 ` Kirill Smelkov
[not found] <alpine.DEB.2.20.1906191227430.3726@hadrien>
2019-06-19 16:27 ` Kirill Smelkov
2019-06-19 19:47 ` Logan Gunthorpe
2019-06-19 20:19 ` Bjorn Helgaas
2019-06-19 20:21 ` Julia Lawall
2019-06-20 7:01 ` kirr
2019-06-21 16:42 ` Sebastian Andrzej Siewior
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=alpine.DEB.2.21.1904180728420.8144@hadrien \
--to=julia.lawall@lip6.fr \
--cc=bigeasy@linutronix.de \
--cc=helgaas@kernel.org \
--cc=kbuild-all@01.org \
--cc=kirr@nexedi.com \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox