From: "Török Edwin" <edwintorok@gmail.com>
To: maciej.rutecki@gmail.com
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request xfs_is_delayed_page
Date: Sun, 24 Jul 2011 14:06:04 +0300 [thread overview]
Message-ID: <4E2BFC9C.3060902@gmail.com> (raw)
In-Reply-To: <201107240914.04145.maciej.rutecki@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On 07/24/2011 10:14 AM, Maciej Rutecki wrote:
> On czwartek, 21 lipca 2011 o 22:55:04 Török Edwin wrote:
>> Hi,
>>
>> Just got this BUG in my dmesg:
>> [47504.938446] BUG: unable to handle kernel paging request at
>> ffff884058ec3270 [47504.938488] IP: [<ffffffff8127baf1>]
> [...]
>
> 2.6.39 works OK?. It is regression?
I don't know, I was not able to reproduce the bug on 3.0 either.
Either the bug was fixed between 3.0-rc7 and 3.0, or it is very hard to reproduce.
I tried with the attached test program (which creates a mess^H some files in the current directory, performs I/O and dumps core
from 2 processes in parallel.).
All I got was 2 hung kernel threads for 2m+ in xfs_evict_inode + xfs_file_sync, trigerring the hung_check timer and NMI backtraces,
and the process was unkillable (by kill -9) for a while. It eventually recovered though, and its not surprising that this happened
: the test program generated 100Mb/s - 500Mb/s I/O.
I'll have to see if I can reproduce the BUG with 3.0-rc7. Although I don't see any XFS changes between 3.0-rc7 and 3.0
there were some RCU fixes to core VFS code.
Best regards,
--Edwin
[-- Attachment #2: alloc4.c --]
[-- Type: text/x-csrc, Size: 2002 bytes --]
#include <stdlib.h>
#include <stdint.h>
#include <unistd.h>
#include <string.h>
#include <pthread.h>
#include <stdio.h>
#include <errno.h>
void alloc_and_die(void)
{
uint64_t i;
uint64_t n = 4*1024*1024*1024ll;
char *x = malloc(n);
printf("touching pages\n");
/* touch each page once */
for (i=0;i<n;i += 4096) {
x[i] = 42;
}
/* wait a bit */
printf("sleeping\n");
/* parallel coredump */
fork();
sleep(10);
printf("Dumping core...\n");
/* now die */
abort();
}
void *iothread(void *dummy)
{
uint16_t data[4000];
char fname[128] = "iothreadXXXXXX";
unsigned int seed = 0x42;
unsigned i;
uint64_t pos = 0;
unsigned counter = 0;
int fd = mkstemp(fname);
if (fd == -1) {
perror("mkstemp");
abort();
}
for (i=0;i<sizeof(data)/sizeof(data[0]);i++) {
data[i] = rand_r(&seed);
}
/* continously write to a 1MB sized file */
while (1) {
if (write(fd, data, sizeof(data)) != sizeof(data)) {
perror("write failed");
abort();
}
pos += sizeof(data);
if (pos > 10*1024*1024ll) {
counter++;
if (counter%2) {
fsync(fd);
lseek(fd, 0, SEEK_SET);
} else {
unlink(fname);
close(fd);
strncpy(fname, "iothreadXXXXXX", sizeof(fname));
fd = mkstemp(fname);
if (fd == -1) {
perror("mkstemp");
abort();
}
}
for (i=0;i<sizeof(data)/sizeof(data[0]);i++) {
data[i] = rand_r(&seed);
}
}
}
return NULL;
}
void run_iothread(void)
{
pthread_t thr;
int rc;
rc = pthread_create(&thr, NULL,
iothread, NULL);
if (rc) {
errno = rc;
perror("pthread_create");
abort();
}
}
int main()
{
switch (fork()) {
case 0:
run_iothread();
run_iothread();
alloc_and_die();
break;
case -1:
perror("fork failed\n");
abort();
break;
default:
run_iothread();
run_iothread();
run_iothread();
run_iothread();
iothread(NULL);
break;
}
return 0;
}
next prev parent reply other threads:[~2011-07-24 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 20:55 BUG: unable to handle kernel paging request xfs_is_delayed_page Török Edwin
2011-07-24 7:14 ` Maciej Rutecki
2011-07-24 11:06 ` Török Edwin [this message]
2011-07-24 18:55 ` Maciej Rutecki
2011-07-25 15:33 ` Paul E. McKenney
2011-07-24 12:17 ` Christoph Hellwig
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=4E2BFC9C.3060902@gmail.com \
--to=edwintorok@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=xfs-masters@oss.sgi.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