linux-kernel - Re: Re: Re: XFS deadlock fixed?

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>] [day] [month] [year] [list]

Date:	Mon, 16 Jan 2012 09:23:36 -0200
From:	Kelbel Junior <jymmyjr@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Re: Re: XFS deadlock fixed?

Hello, everybody.
It appeared that same error message when using kernel version 2.6.38.8 ...

Several lines in /var/log/messages with:
kernel: XFS: possible memory allocation deadlock in kmem_alloc (mode: 0x250)

Does anyone know know if this bug has been fixed in newer versions of
Linux kernel? 3.x maybe?



Thanks.
Kelbel Junior


2011/5/11 Christoph Hellwig <>

    And here's the actual patch, sorry:


    Index: linux-2.6/fs/xfs/linux-2.6/kmem.c
    ===================================================================
    --- linux-2.6.orig/fs/xfs/linux-2.6/kmem.c	2011-05-11
17:29:51.729191621 +0200

    +++ linux-2.6/fs/xfs/linux-2.6/kmem.c	2011-05-11 17:30:22.915689382 +0200
    @@ -56,10 +56,12 @@ kmem_alloc(size_t size, unsigned int __n
     		ptr = kmalloc(size, lflags);
     		if (ptr || (flags & (KM_MAYFAIL|KM_NOSLEEP)))

     			return ptr;
    -		if (!(++retries % 100))
    +		if (!(++retries % 100)) {
     			xfs_err(NULL,
     		"possible memory allocation deadlock in %s (mode:0x%x)",
     					__func__, lflags);
    +			dump_stack();

    +		}
     		congestion_wait(BLK_RW_ASYNC, HZ/50);
     	} while (1);
     }
    @@ -112,10 +114,12 @@ kmem_zone_alloc(kmem_zone_t *zone, unsig
     		ptr = kmem_cache_alloc(zone, lflags);
     		if (ptr || (flags & (KM_MAYFAIL|KM_NOSLEEP)))

     			return ptr;
    -		if (!(++retries % 100))
    +		if (!(++retries % 100)) {
     			xfs_err(NULL,
     		"possible memory allocation deadlock in %s (mode:0x%x)",
     					__func__, lflags);
    +			dump_stack();

    +		}
     		congestion_wait(BLK_RW_ASYNC, HZ/50);
     	} while (1);
     }


    2011/5/11 Christoph Hellwig <>

        You're probably running into a different issue.  Any chance you can try
        the attached patch to see where you're stuck exactly?

        Also in case you're using slub (CONFIG_SLUB) can you check if it still

        happens when using slab (CONFIG_SLAB) instead?


        2011/5/10 Felipe Wilhelms Damasio - Taghos <>

                Hi Mr. Hellwig,

                I saw the XFS deadlock thread regarding 2.6.38:

            http://www.linux.sgi.com/archives/xfs/2011-03/msg00185.html


                I'm seeing too in 2.6.38.4. A lot of

            XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)

                I checked the changelog for 2.6.38.6 and can't be sure
if the fix got
            in...could you tell me if it did?


                Thanks,

            --

            Felipe Wilhelms Damasio


            TAGHOS - Tecnologia
            Rua Prof. Alvaro Alvim, 211
            Porto Alegre - RS - (51) 3239-3180
            www.taghos.com.br <http://www.taghos.com.br/>
--
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/