linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonlist@gmail.com>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/ext4/inode.c:2982!
Date: Fri, 17 Oct 2014 02:03:45 +0400	[thread overview]
Message-ID: <87egu7k6ym.fsf@openvz.org> (raw)
In-Reply-To: <20141016201504.GA24798@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1702 bytes --]

Dave Jones <davej@redhat.com> writes:

> On Thu, Oct 16, 2014 at 10:33:46AM -0400, Dave Jones wrote:
>
>  >  > Try this patch http://www.spinics.net/lists/linux-ext4/msg45683.html
>  > 
>  > I'll give it a try if I can get it reproducing easily, otherwise I cna't say
>  > either way whether the patch is doing any good.
>
> ok, I managed to reproduce it a few times, and then tried again with
> your patch.  I'm not sure if it's related, but I'm now seeing lockups
> in ext4.  The process that gets stuck looks like this..
99.99% this one is not related. This is just one more uncovered one
by trinity magics. Looks like I've got what is wrong
lseek SEEK_HOLE/SEEK_DATA try to find block allocated one by one
instead of using ext4_ext_next_allocated_block() COMMIT c8c0df24
Plese look an my test below. I'm too tired for today (especially
after Gone girl the movie). I'll send patch tomorrow.
>
> trinity-c21     R  running task    13232  9781    831 0x10000004
>  0000000000000000 0000000000000001 0000000000000000 0000000000000000
>  ffff8800c8d333d8 0000000000000000 0000000000000002 00000000cacaa650
>  ffff880217cf7db8 0000000000000000 0000000000000000 ffffffffa929ff8c
> Call Trace:
>  [<ffffffffa929ff8c>] ? ext4_map_blocks+0x31c/0x560
>  [<ffffffffa929fe75>] ? ext4_map_blocks+0x205/0x560
>  [<ffffffffa92e689c>] ? ext4_es_find_delayed_extent_range+0x48c/0x4e0
>  [<ffffffffa9298fe1>] ? ext4_llseek+0x261/0x3f0
>  [<ffffffffa922e6e9>] ? __fdget_pos+0x49/0x50
>  [<ffffffffa90e484e>] ? rcu_read_lock_held+0x6e/0x80
>  [<ffffffffa920ca44>] ? SyS_lseek+0x94/0xc0
>
> I've got to run right now, but I'll look into tracing it some more when I get back.
>
> 	Dave

[-- Attachment #1.2: Type: application/pgp-signature, Size: 818 bytes --]

[-- Attachment #2: lseek.c --]
[-- Type: text/plain, Size: 616 bytes --]

/*
 * regression test for bug in ext4_seek_data
 *  (C) Dmitry Monakhov 
 * original report https://lkml.org/lkml/2014/10/16/620
 */		
#define _GNU_SOURCE
#define _LARGEFILE_SOURCE
#define _FILE_OFFSET_BITS 64
#include <sys/types.h>
#include <unistd.h>
#include <fcntl.h>

#ifndef SEEK_DATA
#define SEEK_DATA       3
#endif

int main(int argc, char **argv)
{
        int fd;
        loff_t size = 1ULL << 40;
        fd = open("test", O_RDWR|O_CREAT, 0777);
        ftruncate(fd, size);
        size = 1ULL << 39;
	/* Next line will likely spin forever :) */
        llseek(fd, size, SEEK_DATA);
        return 0;
}

  reply	other threads:[~2014-10-16 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  5:57 kernel BUG at fs/ext4/inode.c:2982! Dave Jones
2014-10-16  9:31 ` Dmitry Monakhov
2014-10-16 14:33   ` Dave Jones
2014-10-16 20:15     ` Dave Jones
2014-10-16 22:03       ` Dmitry Monakhov [this message]
2014-10-17 13:25         ` [PATCH] ext4: fix suboptimal seek_{data,hole} extents traversial Dmitry Monakhov
2014-11-25 21:14           ` Theodore Ts'o
2014-11-27 14:48             ` Dmitry Monakhov
2014-11-28 15:02             ` Dmitry Monakhov
2014-11-29 17:52               ` Theodore Ts'o
2014-12-01 11:25                 ` Dmitry Monakhov
2014-10-17 17:27         ` kernel BUG at fs/ext4/inode.c:2982! Dave Jones

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=87egu7k6ym.fsf@openvz.org \
    --to=dmonlist@gmail.com \
    --cc=davej@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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).