From: Brian King <brking@linux.vnet.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: James.Bottomley@suse.de, nab@linux-iscsi.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/3] tcm ibmvscsis driver
Date: Mon, 21 Mar 2011 07:56:18 -0500 [thread overview]
Message-ID: <4D874AF2.3090602@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110321100909E.fujita.tomonori@lab.ntt.co.jp>
On 03/20/2011 08:09 PM, FUJITA Tomonori wrote:
> Thanks for the testings,
>
> On Fri, 18 Mar 2011 15:58:53 -0500
> Brian King <brking@linux.vnet.ibm.com> wrote:
>
>> On 03/07/2011 08:40 AM, James Bottomley wrote:
>>> On Mon, 2011-03-07 at 13:41 +0900, FUJITA Tomonori wrote:
>>>> On Sat, 12 Feb 2011 14:27:26 -0600
>>>> James Bottomley <James.Bottomley@suse.de> wrote:
>>>>
>>>>>> Disregard my previous comment. It looks like current client should handle reservations
>>>>>> just fine without any further changes.
>>>>>
>>>>> So is that an ack for putting this in scsi-misc ... or did you want to
>>>>> do more testing first?
>>>>
>>>> Ping,
>>>>
>>>> Brian, James, can we merge this during the next merge window?
>>>
>>> I'm still waiting for an ack from Brian.
>>
>> Sorry for the delay... I've got this loaded in the lab and have managed to oops
>> a couple times. The first one was during shutdown, which I wasn't able to collect
>> any data for. The most recent occurred when a client was trying to login for the
>> first time:
>
> You mean that the kernel crashes every time when a client logs in?
That is correct. This occurs whether or not there are any virtual disks defined. This
is occurring with current linus git head plus the three patches that were posted.
-Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next prev parent reply other threads:[~2011-03-21 12:56 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 12:21 [PATCH 0/3] ibmvscsis driver rewrite FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 1/3] libsrp: add srp_data_length helper function FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 2/3] libsrp: fix dma_unmap_sg FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 3/3] tcm ibmvscsis driver FUJITA Tomonori
2011-02-10 19:03 ` Nicholas A. Bellinger
2011-02-14 1:36 ` FUJITA Tomonori
2011-02-14 3:26 ` FUJITA Tomonori
2011-02-14 9:01 ` Nicholas A. Bellinger
2011-02-14 9:29 ` FUJITA Tomonori
2011-02-14 9:27 ` Nicholas A. Bellinger
2011-02-14 9:46 ` FUJITA Tomonori
2011-02-14 9:51 ` Nicholas A. Bellinger
2011-02-10 19:15 ` Brian King
2011-02-10 19:38 ` Nicholas A. Bellinger
2011-02-11 21:13 ` Brian King
2011-02-12 20:27 ` James Bottomley
2011-03-07 4:41 ` FUJITA Tomonori
2011-03-07 6:17 ` Nicholas A. Bellinger
2011-03-07 6:24 ` FUJITA Tomonori
2011-03-07 6:55 ` Nicholas A. Bellinger
2011-03-07 14:40 ` James Bottomley
2011-03-18 16:57 ` James Bottomley
2011-03-18 20:58 ` Brian King
2011-03-18 22:09 ` Nicholas A. Bellinger
2011-03-19 14:32 ` James Bottomley
2011-03-21 1:09 ` FUJITA Tomonori
2011-03-21 12:56 ` Brian King [this message]
2011-03-21 21:01 ` Brian King
2011-03-21 21:01 ` Nicholas A. Bellinger
2011-03-21 21:24 ` Brian King
2011-03-21 22:29 ` Nicholas A. Bellinger
2011-03-21 23:20 ` FUJITA Tomonori
2011-03-21 23:50 ` Nicholas A. Bellinger
2011-03-21 23:55 ` FUJITA Tomonori
2011-03-22 0:26 ` Nicholas A. Bellinger
2011-03-22 0:32 ` FUJITA Tomonori
2011-03-22 2:28 ` Nicholas A. Bellinger
2011-03-22 3:26 ` FUJITA Tomonori
2011-03-21 21:05 ` James Bottomley
2011-03-21 22:37 ` Brian King
2011-03-21 22:22 ` Brian King
2011-03-21 22:31 ` Brian King
2011-03-21 22:48 ` Nicholas A. Bellinger
2011-03-22 12:53 ` Brian King
2011-03-22 22:06 ` Nicholas A. Bellinger
2011-03-22 22:49 ` FUJITA Tomonori
2011-03-23 1:35 ` Nicholas A. Bellinger
2011-03-23 5:12 ` FUJITA Tomonori
2011-03-23 8:26 ` Nicholas A. Bellinger
2011-03-23 8:48 ` FUJITA Tomonori
2011-03-23 10:00 ` Nicholas A. Bellinger
2011-03-23 12:04 ` FUJITA Tomonori
2011-03-23 21:17 ` Nicholas A. Bellinger
2011-03-24 1:54 ` FUJITA Tomonori
2011-03-24 7:29 ` Nicholas A. Bellinger
2011-03-23 15:19 ` Brian King
2011-03-23 20:34 ` Nicholas A. Bellinger
2011-03-25 14:33 ` Brian King
2011-03-25 20:13 ` Nicholas A. Bellinger
2011-03-21 22:34 ` Nicholas A. Bellinger
2011-03-21 23:06 ` FUJITA Tomonori
2011-03-21 23:13 ` Nicholas A. Bellinger
2011-03-21 23:22 ` FUJITA Tomonori
2011-03-22 0:03 ` Nicholas A. Bellinger
2011-03-21 23:30 ` FUJITA Tomonori
2011-02-14 1:42 ` FUJITA Tomonori
2011-02-14 1:42 ` FUJITA Tomonori
2011-02-14 7:16 ` Bart Van Assche
2011-02-14 9:11 ` FUJITA Tomonori
2011-02-14 9:18 ` Nicholas A. Bellinger
2011-02-14 9:19 ` Nicholas A. Bellinger
2011-02-14 9:31 ` FUJITA Tomonori
2011-02-14 9:29 ` Nicholas A. Bellinger
2011-02-14 11:50 ` Bart Van Assche
2011-02-15 3:42 ` FUJITA Tomonori
2011-02-15 19:20 ` Bart Van Assche
2011-02-15 23:21 ` FUJITA Tomonori
2011-02-10 18:34 ` [PATCH 0/3] ibmvscsis driver rewrite Nicholas A. Bellinger
2011-02-14 1:36 ` FUJITA Tomonori
2011-02-14 8:48 ` Nicholas A. Bellinger
[not found] ` <4D53DE96.2020502@suse.de>
[not found] ` <1297363312.18212.153.camel@haakon2.linux-iscsi.org>
2011-02-10 21:22 ` 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=4D874AF2.3090602@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@suse.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.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;
as well as URLs for NNTP newsgroup(s).