From: Eric Sandeen <sandeen@sandeen.net>
To: Chris Holcombe <cholcombe@box.com>
Cc: Blake Golliher <bgolliher@box.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org
Subject: Re: XFS: possible memory allocation deadlock in kmem_alloc
Date: Tue, 5 Nov 2019 14:08:27 -0600 [thread overview]
Message-ID: <982194a0-4ab4-d3ca-dfc0-31427ace87fe@sandeen.net> (raw)
In-Reply-To: <CAL3_v4P+HwxegYCO3czD56nT0rGTwZ=qgDLOWAoppOR=6mMZ+Q@mail.gmail.com>
I don't think that's the information I requested:
>> Can you please do:
>>
>> # echo 11 > /proc/sys/fs/xfs/error_level
>>
>> and hit it again, then send a few of the backtraces from dmesg?
-Eric
On 11/5/19 1:53 PM, Chris Holcombe wrote:
> I've got the stack traces and they're massive.
> https://cloud.box.com/s/5grgnjwej5prmahl92v49937w6hgdnsv
> https://cloud.box.com/s/wfrjg7yhiwufpgidoq1qos8mrwtu4ij3
> https://cloud.box.com/s/3wcfgfdyvcsbslfdxc9ntfdt7yrhtcjt
>
> On Tue, Nov 5, 2019 at 9:11 AM Eric Sandeen <sandeen@sandeen.net> wrote:
>>
>>
>>
>> CAUTION: External Email
>>
>>
>>
>>
>> On 11/5/19 10:25 AM, Chris Holcombe wrote:
>>> Hi Eric,
>>> I've attached both the dmesg command output and /var/log/dmesg.log
>>> which have different values in them.
>>
>> Thanks. Aaand .... I forgot that we don't dump a stack trace by default.
>>
>> Can you please do:
>>
>> # echo 11 > /proc/sys/fs/xfs/error_level
>>
>> and hit it again, then send a few of the backtraces from dmesg?
>>
>> # echo 3 > /proc/sys/fs/xfs/error_level
>>
>> will quiet things down again.
>>
>> -Eric
>
next prev parent reply other threads:[~2019-11-05 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 23:38 XFS: possible memory allocation deadlock in kmem_alloc Chris Holcombe
2019-11-05 0:01 ` Darrick J. Wong
2019-11-05 0:31 ` Eric Sandeen
[not found] ` <CAC752AmahECFry9x=pvqDkwQUj1PEJjoWGa2KFG1uaTzT1Bbnw@mail.gmail.com>
2019-11-05 4:21 ` Eric Sandeen
2019-11-05 16:25 ` Chris Holcombe
2019-11-05 17:11 ` Eric Sandeen
2019-11-05 19:53 ` Chris Holcombe
2019-11-05 20:08 ` Eric Sandeen [this message]
[not found] ` <CAC752AnZ4biDGk6V17URQm5YVp=MwZBhiMH8=t733zaypxUsmA@mail.gmail.com>
2019-11-05 20:47 ` Eric Sandeen
[not found] ` <CAC752A=y9PMEQ1e4mXskha1GFeKXWi8PsdBW-nX40pgFCYp1Uw@mail.gmail.com>
2019-11-05 21:23 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2016-05-30 4:45 baotiao
2016-05-30 5:04 ` Dave Chinner
2016-05-30 8:48 ` baotiao
2016-05-30 9:20 ` Carlos Maiolino
2016-05-31 2:43 ` 陈宗志
2016-05-31 3:10 ` Dave Chinner
2016-05-31 11:00 ` 陈宗志
2016-05-31 12:14 ` Carlos Maiolino
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=982194a0-4ab4-d3ca-dfc0-31427ace87fe@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bgolliher@box.com \
--cc=cholcombe@box.com \
--cc=darrick.wong@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).