From: Eric Sandeen <sandeen@sandeen.net>
To: Stefan Ring <stefanrin@gmail.com>
Cc: Jan Kokoska <jan@glow.cz>, Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: Kernel crashes with trace ending in XFS code on RHEL6 variant kernel
Date: Tue, 28 Oct 2014 15:06:45 -0500 [thread overview]
Message-ID: <544FF755.1010705@sandeen.net> (raw)
In-Reply-To: <CAAxjCEyTq5UfmqzBbtXXQ=vWoHmCG5WJvLGsSwCfRL0P4qnCJw@mail.gmail.com>
On 10/28/14 3:01 PM, Stefan Ring wrote:
> On Tue, Oct 28, 2014 at 6:42 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>> On 10/28/14 10:38 AM, Jan Kokoska wrote:
>>> Hi,
>>>
>>> I'm running OpenVZ (OS container) kernel variant of RHEL6 kernel on
>>
>> ... for which we have no source code? ;)
>>
>> I don't know what's in "2.6.32-openvz-amd64" so can't help much.
>>
>> What is at line 86 of xfs_aops.c in that kernel?
>
> From my quick investigation, it would seem to be the line "bh = head =
> page_buffers(page);" of xfs_count_page_state.
Yes, I think you're right, but my point is this is a kernel which we don't
maintain.
Anyway, I don't know for sure offhand what this could be;
upstream ef5d437f71afdf4afdbab99213add99f4b1318fd looks related, but
TBH I'm not sure if it's specific to S390.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-28 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 15:38 Kernel crashes with trace ending in XFS code on RHEL6 variant kernel Jan Kokoska
2014-10-28 17:42 ` Eric Sandeen
2014-10-28 20:01 ` Stefan Ring
2014-10-28 20:06 ` Eric Sandeen [this message]
2014-10-29 10:00 ` Jan Kokoska
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=544FF755.1010705@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jan@glow.cz \
--cc=stefanrin@gmail.com \
--cc=xfs@oss.sgi.com \
/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