lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <471C1D29.5020403@gmail.com>
Date: Sun, 21 Oct 2007 23:46:49 -0400
From: emist <emistz@...il.com>
To: Linux <linux-kernel@...r.kernel.org>
CC: geraldsc@...ibm.com, cotte@...ibm.com, linux390@...ibm.com,
linux-s390@...r.kernel.org
Subject: Re: [PATCH] Bug fix for the s390 dcssblk driver
Heiko Carstens wrote:
> On Sat, Oct 20, 2007 at 01:24:34PM -0400, emist wrote:
>> 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@...r.kernel.org list and
>>> possibly also the maintainer at linux390@...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.
>
> Gerald or Carsten (cc'ed) should look into this.
> Thanks for reporting.
>
Hello,
I realized that I did not fix one of the cases where this bug manifests
in my last patch. Here is the complete patch to fix the issue. And this
time I cc'ed the relevant people.
Have a good one,
Igor H.
View attachment "dcssblk_fix" of type "text/plain" (1540 bytes)
Powered by blists - more mailing lists