Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1590382 > unrolled thread

Re: Poll CQ syncing problem

Started byChristoph Hellwig <hch@lst.de>
First post2017-03-01 16:10 +0100
Last post2017-03-01 16:10 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Poll CQ syncing problem Christoph Hellwig <hch@lst.de> - 2017-03-01 16:10 +0100

#1590382 — Re: Poll CQ syncing problem

FromChristoph Hellwig <hch@lst.de>
Date2017-03-01 16:10 +0100
SubjectRe: Poll CQ syncing problem
Message-ID<tge38-4N8-17@gated-at.bofh.it>
On Wed, Mar 01, 2017 at 04:30:26PM +0200, Noa Osherovich wrote:
> Analysis:
> Since ib_comp_wq isn't single threaded, two works can run in parallel for the same CQ,
> executing __ib_process_cq.

They shouldn't.  Each CQ has a single work_struct, and any given work_struct
should only be executing at once:

"Note that the flag ``WQ_NON_REENTRANT`` no longer exists as all
workqueues are now non-reentrant - any work item is guaranteed to be
executed by at most one worker system-wide at any given time."

> Since this function isn't thread safe and the wc array is shared, it causes a data corruption
> which eventually crashes in the MAD layer due to a double list_del of the same element.

This should not be the case.  What kernel version are you testing and does
it contain any patches touching core kernel code?

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web