public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: emist <emistz@gmail.com>
Cc: Linux <linux-kernel@vger.kernel.org>,
	geraldsc@de.ibm.com, cotte@de.ibm.com, linux390@de.ibm.com,
	linux-s390@vger.kernel.org, Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] Bug fix for the s390 dcssblk driver
Date: Mon, 22 Oct 2007 13:37:23 +0200	[thread overview]
Message-ID: <20071022133723.089b84db@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <471C1D29.5020403@gmail.com>

On Sun, 21 Oct 2007 23:46:49 -0400,
emist <emistz@gmail.com> wrote:

> # This patch fixes a memory corruption bug in the s390 dcssblk driver.
> # The bug occurs when an attempt to change the type of a segment
> # returns an error. At this point the driver tries to remove the segment in
> # question while some of the device's attributes are in use. This causes the
> # driver to hang.

Hm, seems we missed another of those device attributes exhibiting
suicidal tendencies...

Tejun has a patchset allowing device attributes to commit suicide (see
http://marc.info/?l=linux-kernel&m=119027371416452&w=2), although I'm
not sure what its current status is. Until then, you would need to use
device_schedule_callback() to commit suicide.

This all of course only applies if killing the segment is better than
leaving it in its current state, but others can make a better judgement
on that :)

  reply	other threads:[~2007-10-22 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200710201451.57138.elendil@planet.nl>
     [not found] ` <471A39D2.1070303@gmail.com>
     [not found]   ` <20071021100926.GA4420@osiris.ibm.com>
2007-10-22  3:46     ` [PATCH] Bug fix for the s390 dcssblk driver emist
2007-10-22 11:37       ` Cornelia Huck [this message]
2007-10-23 13:22         ` Gerald Schaefer

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=20071022133723.089b84db@gondolin.boeblingen.de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=emistz@gmail.com \
    --cc=geraldsc@de.ibm.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux390@de.ibm.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