public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 208805] New: XFS: iozone possible memory allocation deadlock
Date: Tue, 04 Aug 2020 09:52:48 +0000	[thread overview]
Message-ID: <bug-208805-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=208805

            Bug ID: 208805
           Summary: XFS: iozone possible memory allocation deadlock
           Product: File System
           Version: 2.5
    Kernel Version: Linux 5.4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: jjzuming@outlook.com
        Regression: No

When I ran iozone to test XFS in a memory insufficient situation,I found that
iozone was blocked and The log "XFS: iozone possible memory allocation
deadlock" was printed.

Reviewing the XFS code, I found that kmem_alloc(), xfs_buf_allocate_memory(),
kmem_zone_alloc() and kmem_realloc() were implemented with "while" loops. These
functions kept trying to get memory while the memory was insufficient, as a
result of which "memory allocation deadlock" happened.

I think it may be a little unreasonable, although it can guarantee that the
memory allocation succeed. Maybe using error handling code to handle the memory
allocation failures is better.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2020-08-04  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  9:52 bugzilla-daemon [this message]
2020-08-26 15:19 ` [Bug 208805] New: XFS: iozone possible memory allocation deadlock Brian Foster
2020-08-26 15:20 ` [Bug 208805] " bugzilla-daemon

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=bug-208805-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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