From: Alexander Gordeev <agordeev@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>, Kent Overstreet <kmo@daterainc.com>,
Shaohua Li <shli@kernel.org>, Christoph Hellwig <hch@lst.de>,
Mike Christie <michaelc@cs.wisc.edu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] percpu_ida: Handle out-of-tags gracefully
Date: Tue, 11 Mar 2014 14:51:38 +0100 [thread overview]
Message-ID: <20140311135137.GA22995@dhcp-26-207.brq.redhat.com> (raw)
In-Reply-To: <531DC851.5060400@acm.org>
On Mon, Mar 10, 2014 at 03:12:33PM +0100, Bart Van Assche wrote:
> Avoid that percpu_ida_alloc() hangs or crashes if there are still
> tags are available. Wait until a tag becomes available instead of
> giving up when running out of tags temporarily. This patch fixes
> the following kernel bug:
Hi Bart,
Few comments below, but the changelog does not correspond to the
actual change in 'Wait until a tag becomes available'.
> ------------[ cut here ]------------
> kernel BUG at lib/percpu_ida.c:81!
> invalid opcode: 0000 [#1] SMP
> RIP: 0010:[<ffffffff8120f00e>] [<ffffffff8120f00e>] percpu_ida_alloc+0x33e/0x370
> Call Trace:
> [<ffffffff811ef95f>] blk_mq_get_tag+0x2f/0x50
> [<ffffffff811ed79c>] blk_mq_alloc_rq.isra.17+0x1c/0x90
> [<ffffffff811eeb9b>] blk_mq_alloc_request_pinned+0x9b/0x110
> [<ffffffff811ef4c6>] blk_mq_make_request+0x426/0x480
> [<ffffffff811e28f0>] generic_make_request+0xc0/0x110
> [<ffffffff811e29ab>] submit_bio+0x6b/0x140
> [<ffffffff8117aabb>] _submit_bh+0x13b/0x220
> [<ffffffff8117d70f>] block_read_full_page+0x1ff/0x300
> [<ffffffff81181128>] blkdev_readpage+0x18/0x20
> [<ffffffff811067b7>] __do_page_cache_readahead+0x277/0x280
> [<ffffffff81106d1d>] force_page_cache_readahead+0x8d/0xc0
> [<ffffffff81106d9b>] page_cache_sync_readahead+0x4b/0x50
> [<ffffffff810fdf05>] generic_file_aio_read+0x4c5/0x700
> [<ffffffff8118147b>] blkdev_aio_read+0x4b/0x70
> [<ffffffff8114a28a>] do_sync_read+0x5a/0x90
> [<ffffffff8114a8cb>] vfs_read+0x9b/0x160
> [<ffffffff8114b389>] SyS_read+0x49/0xa0
> [<ffffffff81416049>] tracesys+0xd0/0xd5
> ---[ end trace cdd1a8a7968266cf ]---
>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> Cc: Kent Overstreet <kmo@daterainc.com>
> Cc: Shaohua Li <shli@kernel.org>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Jens Axboe <axboe@kernel.dk>
> Cc: Alexander Gordeev <agordeev@redhat.com>
> Cc: Mike Christie <michaelc@cs.wisc.edu>
> ---
> lib/percpu_ida.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/lib/percpu_ida.c b/lib/percpu_ida.c
> index 93d145e..170d27c 100644
> --- a/lib/percpu_ida.c
> +++ b/lib/percpu_ida.c
> @@ -73,7 +73,7 @@ static inline void steal_tags(struct percpu_ida *pool,
> if (cpu >= nr_cpu_ids) {
> cpu = cpumask_first(&pool->cpus_have_tags);
> if (cpu >= nr_cpu_ids)
> - BUG();
> + break;
I assume the BUG() above hits? If so, I am failing to understand how
the code gets here. Mind elaborate?
> }
>
> pool->cpu_last_stolen = cpu;
> @@ -189,6 +189,9 @@ int percpu_ida_alloc(struct percpu_ida *pool, int state)
> spin_unlock(&pool->lock);
> local_irq_restore(flags);
>
> + if (tags->nr_free)
> + wake_up(&pool->wait);
> +
How 'tags->nr_free' could be checked out of locks?
Why waking up another thread instead of returning the tag on this CPU?
Why 'percpu_max_size' threshold is ignored?
Anyway, IMHO the above BUG() indicates a problem elsewhere.
> if (tag >= 0 || state == TASK_RUNNING)
> break;
>
> --
> 1.8.4.5
>
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-03-11 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 14:12 Bart Van Assche
2014-03-11 13:51 ` Alexander Gordeev [this message]
2014-03-11 18:10 ` Bart Van Assche
2014-03-11 20:48 ` Alexander Gordeev
2014-03-12 7:22 ` Bart Van Assche
2014-03-12 8:41 ` Alexander Gordeev
2014-03-12 10:05 ` Bart Van Assche
2014-03-12 15:21 ` Alexander Gordeev
2014-03-12 16:16 ` Bart Van Assche
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=20140311135137.GA22995@dhcp-26-207.brq.redhat.com \
--to=agordeev@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=shli@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®