From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
linux-scsi@vger.kernel.org
Subject: Re: uas: kernel BUG at block/blk-tag.c:89 is back again :|
Date: Tue, 08 Jul 2014 12:35:56 +0200 [thread overview]
Message-ID: <53BBC98C.4070004@kernel.dk> (raw)
In-Reply-To: <20140708095619.GA11196@infradead.org>
On 2014-07-08 11:56, Christoph Hellwig wrote:
> On Tue, Jul 08, 2014 at 11:54:14AM +0200, Jens Axboe wrote:
>>> I've posted the patch in reply to another report and added Jens to the
>>> Cc list. As the block maintainer he need to review and merge it.
>>
>> Which patch is this?
>
> This one:
>
> ---
> From: Christoph Hellwig <hch@lst.de>
> Subject: block: don't assume last put of shared tags is for the host
>
> There is no inherent reason why the last put of a tag structure must be
> the one for the Scsi_Host, as device model objects can be held for
> arbitrary periods. Merge blk_free_tags and __blk_free_tags into a single
> funtion that just release a references and get rid of the BUG() when the
> host reference wasn't the last.
Thanks, applied. I don't think I was ever CC'ed on this one, though.
--
Jens Axboe
next prev parent reply other threads:[~2014-07-08 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 13:16 uas: kernel BUG at block/blk-tag.c:89 is back again :| Hans de Goede
2014-07-03 6:01 ` Christoph Hellwig
2014-07-06 12:24 ` Hans de Goede
2014-07-07 10:10 ` Christoph Hellwig
2014-07-07 12:42 ` Hans de Goede
2014-07-08 9:53 ` Christoph Hellwig
2014-07-08 9:54 ` Jens Axboe
2014-07-08 9:56 ` Christoph Hellwig
2014-07-08 10:35 ` Jens Axboe [this message]
2014-07-08 11:25 ` Hans de Goede
2014-07-08 11:40 ` Jens Axboe
2014-07-21 8:15 ` Hans de Goede
2014-07-21 8:17 ` Jens Axboe
2014-07-21 9:10 ` Hans de Goede
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=53BBC98C.4070004@kernel.dk \
--to=axboe@kernel.dk \
--cc=JBottomley@parallels.com \
--cc=hch@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.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;
as well as URLs for NNTP newsgroup(s).