From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752521Ab1GXLGO (ORCPT ); Sun, 24 Jul 2011 07:06:14 -0400 Received: from mail-fx0-f52.google.com ([209.85.161.52]:57069 "EHLO mail-fx0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752270Ab1GXLGI (ORCPT ); Sun, 24 Jul 2011 07:06:08 -0400 Message-ID: <4E2BFC9C.3060902@gmail.com> Date: Sun, 24 Jul 2011 14:06:04 +0300 From: =?ISO-8859-1?Q?T=F6r=F6k_Edwin?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11 MIME-Version: 1.0 To: maciej.rutecki@gmail.com CC: xfs-masters@oss.sgi.com, xfs@oss.sgi.com, Linux Kernel Mailing List Subject: Re: BUG: unable to handle kernel paging request xfs_is_delayed_page References: <4E289228.4000208@gmail.com> <201107240914.04145.maciej.rutecki@gmail.com> In-Reply-To: <201107240914.04145.maciej.rutecki@gmail.com> X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="------------070707050002040803000702" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is a multi-part message in MIME format. --------------070707050002040803000702 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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: [] > [...] > > 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 --------------070707050002040803000702 Content-Type: text/x-csrc; name="alloc4.c" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="alloc4.c" #include #include #include #include #include #include #include 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 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