From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alex Dubov <oakad@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 memstick: support for legacy sony memsticks
Date: Tue, 25 Sep 2012 21:34:39 +0200 [thread overview]
Message-ID: <1348601679.12068.17.camel@maxim-laptop> (raw)
In-Reply-To: <20120925180235.GC16296@google.com>
On Tue, 2012-09-25 at 11:02 -0700, Tejun Heo wrote:
> Hello,
>
> > * Swithced to using a workqueue.
> > Unfortunelly, I still see that workqueue items are executed in parallel
> > I suspect that this happens if one work item sleeps. In this case I
> > don't want other work items to run too. I fixed this with a mutex, and anyway
> > it nice to have it to guaranteee this.
>
> You can use alloc_ordered_workqueue("namefmt", WQ_MEM_RECLAIM). No
> mutex needed for inter-work exclusion.
But this just adds the WQ_UNBOUND. Dunno, without lock I had several
crashes, that for high level of confidence caused by by parallel
execution of work items. Once I added this mutex, I couldnt reproduce
these.
I had the __blk_end_request fail with NULL msb->req. I can't see how
that can happen if work queue isn't executed in parallel.
(and then the I didn't even had by mistake the code that sets it to NULL
in msb_stop, so I really fail to see how that could happen due internal
bug in my code.
>
> Thanks.
>
--
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2012-09-25 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 8:38 Maxim Levitsky
2012-09-25 8:38 ` [PATCH 1/2] scatterlist: add sg_nents Maxim Levitsky
2012-09-25 8:38 ` [PATCH 2/2] memstick: add support for legacy memorysticks Maxim Levitsky
2012-09-25 18:25 ` Tejun Heo
2012-09-25 19:26 ` Maxim Levitsky
2012-09-25 19:38 ` Tejun Heo
2012-09-25 20:24 ` Maxim Levitsky
2012-09-25 18:02 ` [PATCH v2 memstick: support for legacy sony memsticks Tejun Heo
2012-09-25 19:34 ` Maxim Levitsky [this message]
2012-09-25 19:40 ` Tejun Heo
2012-09-25 20:13 ` Maxim Levitsky
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=1348601679.12068.17.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®