From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Kaike Wan <kaike.wan@intel.com>
Subject: Re: [PATCH for-rc] IB/hfi1: Insure pq is not left on waitlist
Date: Wed, 18 Mar 2020 20:49:38 -0300 [thread overview]
Message-ID: <20200318234938.GA19965@ziepe.ca> (raw)
In-Reply-To: <20200317160510.85914.22202.stgit@awfm-01.aw.intel.com>
On Tue, Mar 17, 2020 at 12:05:10PM -0400, Dennis Dalessandro wrote:
> +static void flush_pq_iowait(struct hfi1_user_sdma_pkt_q *pq)
> +{
> + unsigned long flags;
> + seqlock_t *lock = pq->busy.lock;
> +
> + if (!lock)
> + return;
> + write_seqlock_irqsave(lock, flags);
> + if (!list_empty(&pq->busy.list)) {
> + list_del_init(&pq->busy.list);
> + pq->busy.lock = NULL;
> + }
> + write_sequnlock_irqrestore(lock, flags);
I'm trying to grasp how a seqlock is protecting a list_empty and
list_del_init, and this seems.. uh.. insane?
The only place that uses seqlock in infiniband is in hfi1
It only calls seqlock_init and write_seqlock
Never read_seqlock
So, this isn't a seqlock, it is a normal spinlock obfuscated as a
seqlock.
Please clean this mess too.
I don't know what to do with this patch, it might well be functionally
right, but everything about reading it screams wrong wrong wrong. I
don't want to send it to Linus in -rc like this.
At least add something to the commit message asking temporary
forgiveness for this madness.
Also s/insure/ensure/, right?
Jason
next prev parent reply other threads:[~2020-03-18 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 16:05 [PATCH for-rc] IB/hfi1: Insure pq is not left on waitlist Dennis Dalessandro
2020-03-18 23:49 ` Jason Gunthorpe [this message]
2020-03-19 21:46 ` Marciniszyn, Mike
2020-03-19 22:04 ` Jason Gunthorpe
2020-03-20 0:26 ` Marciniszyn, Mike
2020-03-20 0:31 ` Jason Gunthorpe
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=20200318234938.GA19965@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=kaike.wan@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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