From: Dmitry Monakhov <dmonakhov@openvz.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: dgilbert@interlog.com, martin.petersen@oracle.com
Subject: scsi_debug: shared dev context, BUG or FEATURE?
Date: Mon, 27 Mar 2017 20:35:58 +0300 [thread overview]
Message-ID: <87tw6e4o75.fsf@dmlp.sw.ru> (raw)
Hi scsi_debug has very strange structure
from one point it supports dynamic number of devices
but from other point context is common for all devices:
- dif_storep (array of t10 dif tuples)
- map_storep (block map for thinprovision)
- fake_storep (in memory data storage)
- sdebug_q_arr (queue array)
So basically we may have many devices with single context which refers
common data. Are any sane reason to share context between devices?
Who use such behaviour?
IMHO this is a pure bug. Please correct me if I'm wrong, I'll plan to
fix that by allocation separate context for each dev.
next reply other threads:[~2017-03-27 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 17:35 Dmitry Monakhov [this message]
2017-03-28 1:41 ` scsi_debug: shared dev context, BUG or FEATURE? Martin K. Petersen
2017-03-28 10:36 ` Dmitry Monakhov
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=87tw6e4o75.fsf@dmlp.sw.ru \
--to=dmonakhov@openvz.org \
--cc=dgilbert@interlog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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