linux-kernel - Re: Block layer still stack abuser?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 22 Feb 2007 06:44:37 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Neil Brown <neilb@...e.de>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Block layer still stack abuser?

Neil Brown wrote:
> On Friday February 16, drzeus-list@...eus.cx wrote:
>   
>> I was wondering if the block layer has been changed into a more serialized
>> manner yet? I've been trying to google this, but so far no luck. I know there
>> was some talk about removing the stack based approach, but I can't find any
>> information about where this went.
>>
>> If it is currently fixed, a pointer to from which version would be nice.
>>     
>
> Might this:
>    http://lkml.org/lkml/2007/2/10/22
>
> relate to your question?
> If you are talking about stacking block device (via dm or md), then a
> patch to fix this in in -mm but there are or were some potential
> issues in dm that seem to be holding it up.
>
>   

Yes, I am. I know there has been general work to reduce stack usage here
and there, but the final suggested solution was to serialize all the
block subsystems so that only one was present on the stack at any given
time.

I was constantly hitting this problem a few years ago when I was running
md+xfs+nfs. The fix was in -mm back then as well. ;)

Rgds

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/