From: emist <emistz@gmail.com>
To: Linux <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Bug fix for the s390 dcssblk driver
Date: Sat, 20 Oct 2007 13:24:34 -0400 [thread overview]
Message-ID: <471A39D2.1070303@gmail.com> (raw)
In-Reply-To: <200710201451.57138.elendil@planet.nl>
Frans Pop wrote:
> emist wrote:
>> The following patch fixes and issue in the s390 dcssblk driver. The
>> issue is caused when an unsuccessful attempt is made in order to change
>> a segment's type through the device attribute file "shared". This causes
>> the driver to remove the device in question, removing with it the device
>> attribute which is currently handling the call. The result is a hang on
>> the driver as it removes memory from under its feet.
>>
>> Not exactly sure if this explanation makes sense or its entirely
>> accurate. This is what I believe at this point from encountering and
>> fixing the error. Anyway here is the patch, hope it helps.
>
> Hi,
>
> If you don't get any reactions to your patch during the next few days, I
> suggest you resend it and then CC the linux-s390@vger.kernel.org list and
> possibly also the maintainer at linux390@de.ibm.com.
>
> In general you should always try to CC the relevant list/people as listed in
> the MAINTAINERS file and not just the linux-kernel list, both for patches
> and when reporting problems.
>
> Cheers,
> Frans Pop
>
Thanks Frans, I will do as you suggest.
Have a good one,
Igor H.
next parent reply other threads:[~2007-10-20 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710201451.57138.elendil@planet.nl>
2007-10-20 17:24 ` emist [this message]
2007-10-21 10:09 ` [PATCH] Bug fix for the s390 dcssblk driver Heiko Carstens
2007-10-22 3:46 ` emist
2007-10-22 11:37 ` Cornelia Huck
2007-10-23 13:22 ` Gerald Schaefer
2007-10-23 22:03 ` emist
2007-10-20 5:07 emist
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=471A39D2.1070303@gmail.com \
--to=emistz@gmail.com \
--cc=linux-kernel@vger.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