All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	chris.mason@oracle.com, david@fromorbit.com, hch@infradead.org,
	akpm@linux-foundation.org, jack@suse.cz
Subject: Re: [PATCH 0/11] Per-bdi writeback flusher threads #4
Date: Wed, 20 May 2009 11:25:28 +0200	[thread overview]
Message-ID: <20090520092528.GP11363@kernel.dk> (raw)
In-Reply-To: <1242811142.2560.33.camel@ymzhang>

On Wed, May 20 2009, Zhang, Yanmin wrote:
> On Wed, 2009-05-20 at 10:54 +0200, Jens Axboe wrote:
> > On Wed, May 20 2009, Jens Axboe wrote:
> > > On Wed, May 20 2009, Zhang, Yanmin wrote:
> > > > On Tue, 2009-05-19 at 08:20 +0200, Jens Axboe wrote:
> > > > > On Tue, May 19 2009, Zhang, Yanmin wrote:
> > > > > > On Mon, 2009-05-18 at 14:19 +0200, Jens Axboe wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > This is the fourth version of this patchset. Chances since v3:
> > > > > > >
> > > > > > > - Dropped a prep patch, it has been included in mainline since.
> > > > > > >
> > > > > > > - Add a work-to-do list to the bdi. This is struct bdi_work. Each
> > > > > > >   wb thread will notice and execute work on bdi->work_list. The arguments
> > > > > > >   are which sb (or NULL for all) to flush and how many pages to flush.
> > > > > > >
> > > > > > > - Fix a bug where not all bdi's would end up on the bdi_list, so potentially
> > > > > > >   some data would not be flushed.
> > > > > > >
> > > > > > > - Make wb_kupdated() pass on wbc->older_than_this so we maintain the same
> > > > > > >   behaviour for kupdated flushes.
> > > > > > >
> > > > > > > - Have the wb thread flush first before sleeping, to avoid losing the
> > > > > > >   first flush on lazy register.
> > > > > > >
> > > > > > > - Rebase to newer kernels.
> > > > 
> > > > > I'm attaching two patches - apply #1 to -rc6, and then #2 is a roll-up
> > > > > of the patch series that you can apply next.
> > > > Jens,
> > > > 
> > > > I run into 2 issues with kernel 2.6.30-rc6+BDI_Flusher_V4. Below is one.
> > > > 
> > > > Tue May 19 00:00:00 CST 2009
> > > > BUG: unable to handle kernel NULL pointer dereference at 00000000000001d8
> > > > IP: [<ffffffff803f3c4c>] generic_make_request+0x10a/0x384
> > > > PGD 0
> > > > Oops: 0000 [#1] SMP
> > > > last sysfs file: /sys/block/sdb/stat
> > > > CPU 0
> > > > Modules linked in: igb
> > > > Pid: 1445, comm: bdi-8:16 Not tainted 2.6.30-rc6-bdiflusherv4 #1 X8DTN
> > > > RIP: 0010:[<ffffffff803f3c4c>]  [<ffffffff803f3c4c>] generic_make_request+0x10a/0x384
> > > > RSP: 0018:ffff8800bd04da60  EFLAGS: 00010206
> > > > RAX: 0000000000000000 RBX: ffff8801be45d500 RCX: 00000000038a0df8
> > > > RDX: 0000000000000008 RSI: 0000000000000576 RDI: ffff8801bf408680
> > > > RBP: ffff8801be45d500 R08: ffffe20001ee8140 R09: ffff8800bd04da98
> > > > R10: 0000000000000000 R11: ffff8800bd72eb40 R12: ffff8801be45d500
> > > > R13: ffff88005f51f310 R14: 0000000000000008 R15: ffff8800b15a5458
> > > > FS:  0000000000000000(0000) GS:ffffc20000000000(0000) knlGS:0000000000000000
> > > > CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> > > > CR2: 00000000000001d8 CR3: 0000000000201000 CR4: 00000000000006e0
> > > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > > > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > > > Process bdi-8:16 (pid: 1445, threadinfo ffff8800bd04c000, task ffff8800bd1b75f0)
> > > > Stack:
> > > >  0000000000000008 ffffffff8027a613 00000000848dc000 ffffffffffffffff
> > > >  ffff8800a8190f50 ffffffff00000012 ffff8800a81938e0 ffffc2000000001b
> > > >  0000000000000000 0000000000000000 ffffe200026f9c30 0000000000000000
> > > > Call Trace:
> > > >  [<ffffffff8027a613>] ? mempool_alloc+0x59/0x10f
> > > >  [<ffffffff803f3f70>] ? submit_bio+0xaa/0xb1
> > > >  [<ffffffff802c6a3f>] ? submit_bh+0xe3/0x103
> > > >  [<ffffffff802c92ea>] ? __block_write_full_page+0x1fb/0x2f2
> > > >  [<ffffffff802c7d6a>] ? end_buffer_async_write+0x0/0xfb
> > > >  [<ffffffff8027e8d2>] ? __writepage+0xa/0x25
> > > >  [<ffffffff8027f036>] ? write_cache_pages+0x21c/0x338
> > > >  [<ffffffff8027e8c8>] ? __writepage+0x0/0x25
> > > >  [<ffffffff8027f195>] ? do_writepages+0x27/0x2d
> > > >  [<ffffffff802c22c1>] ? __writeback_single_inode+0x159/0x2b3
> > > >  [<ffffffff8071e52a>] ? thread_return+0x3e/0xaa
> > > >  [<ffffffff8027f267>] ? determine_dirtyable_memory+0xd/0x1d
> > > >  [<ffffffff8027f2dd>] ? get_dirty_limits+0x1d/0x255
> > > >  [<ffffffff802c27bc>] ? generic_sync_wb_inodes+0x1b4/0x220
> > > >  [<ffffffff802c3130>] ? wb_do_writeback+0x16c/0x215
> > > >  [<ffffffff802c323e>] ? bdi_writeback_task+0x65/0x10d
> > > >  [<ffffffff8024cc06>] ? autoremove_wake_function+0x0/0x2e
> > > >  [<ffffffff8024cb27>] ? bit_waitqueue+0x10/0xa0
> > > >  [<ffffffff80289257>] ? bdi_start_fn+0x0/0xba
> > > >  [<ffffffff802892c6>] ? bdi_start_fn+0x6f/0xba
> > > >  [<ffffffff8024c860>] ? kthread+0x54/0x80
> > > >  [<ffffffff8020c97a>] ? child_rip+0xa/0x20
> > > >  [<ffffffff8024c80c>] ? kthread+0x0/0x80
> > > >  [<ffffffff8020c970>] ? child_rip+0x0/0x20
> > > > 
> 
> 
> > 
> > I found one issue yesterday and one today that could cause issues, not
> > sure it would explain this one. But at least it's worth a try, if it's
> > reproducible.
> I just reproduced it a moment ago manually.
> 
> [global]
> direct=0
> ioengine=mmap
> iodepth=256
> iodepth_batch=32
> size=4G
> bs=4k
> pre_read=1
> overwrite=1
> numjobs=1
> loops=5
> runtime=600
> group_reporting
> directory=/mnt/stp/fiodata
> [job_group0_sub0]
> startdelay=0
> rw=randwrite
> filename=data0/f1:data0/f2
> 
> 
> The fio includes my preread patch to flush files to memory.
> 
> Before starting the second testing, I did a cache dropping by:
> #echo "3">/proc/sys/vm/drop_caches.
> 
> I suspect the drop_caches trigger it.

Thanks, will try this. What filesystem and mount options did you use?

> >  I'm attaching the three patches I have against the posted
> > series. The one in the middle is just an optimization, the first and
> > third are the bug fixes.
> I will test it tomorrow.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Jens Axboe


  reply	other threads:[~2009-05-20  9:25 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 12:19 [PATCH 0/11] Per-bdi writeback flusher threads #4 Jens Axboe
2009-05-18 12:19 ` [PATCH 01/11] writeback: move dirty inodes from super_block to backing_dev_info Jens Axboe
2009-05-18 12:19 ` [PATCH 02/11] writeback: switch to per-bdi threads for flushing data Jens Axboe
2009-05-19 10:20   ` Richard Kennedy
2009-05-19 12:23     ` Jens Axboe
2009-05-19 13:45       ` Richard Kennedy
2009-05-19 17:56         ` Jens Axboe
2009-05-19 22:11           ` Peter Zijlstra
2009-05-20 11:18   ` Jan Kara
2009-05-20 11:32     ` Jens Axboe
2009-05-20 12:11       ` Jan Kara
2009-05-20 12:16         ` Jens Axboe
2009-05-20 12:24           ` Christoph Hellwig
2009-05-20 12:48             ` Jens Axboe
2009-05-20 12:37   ` Christoph Hellwig
2009-05-20 12:49     ` Jens Axboe
2009-05-20 14:02       ` Anton Altaparmakov
2009-05-20 14:02         ` Anton Altaparmakov
2009-05-18 12:19 ` [PATCH 03/11] writeback: get rid of pdflush completely Jens Axboe
2009-05-18 12:19 ` [PATCH 04/11] writeback: separate the flushing state/task from the bdi Jens Axboe
2009-05-20 11:34   ` Jan Kara
2009-05-20 11:39     ` Jens Axboe
2009-05-20 12:06       ` Jan Kara
2009-05-20 12:09         ` Jens Axboe
2009-05-18 12:19 ` [PATCH 05/11] writeback: support > 1 flusher thread per bdi Jens Axboe
2009-05-18 12:19 ` [PATCH 06/11] writeback: include default_backing_dev_info in writeback Jens Axboe
2009-05-18 12:19 ` [PATCH 07/11] writeback: allow sleepy exit of default writeback task Jens Axboe
2009-05-18 12:19 ` [PATCH 08/11] writeback: btrfs must register its backing_devices Jens Axboe
2009-05-18 12:19 ` [PATCH 09/11] writeback: add some debug inode list counters to bdi stats Jens Axboe
2009-05-18 12:19 ` [PATCH 10/11] writeback: add name to backing_dev_info Jens Axboe
2009-05-18 12:19 ` [PATCH 11/11] writeback: check for registered bdi in flusher add and inode dirty Jens Axboe
2009-05-19  6:11 ` [PATCH 0/11] Per-bdi writeback flusher threads #4 Zhang, Yanmin
2009-05-19  6:20   ` Jens Axboe
2009-05-19  6:43     ` Zhang, Yanmin
2009-05-20  7:51     ` Zhang, Yanmin
2009-05-20  7:51       ` Zhang, Yanmin
2009-05-20  8:09       ` Jens Axboe
2009-05-20  8:54         ` Jens Axboe
2009-05-20  9:19           ` Zhang, Yanmin
2009-05-20  9:25             ` Jens Axboe [this message]
2009-05-20 11:19               ` Jens Axboe
2009-05-21  6:33                 ` Zhang, Yanmin
2009-05-21  9:10                   ` Jan Kara
2009-05-22  1:28                     ` Zhang, Yanmin
2009-05-22  8:15                       ` Jens Axboe
2009-05-22 20:44                         ` Jens Axboe
2009-05-23 19:15                           ` Jens Axboe
2009-05-25  8:02                             ` Zhang, Yanmin
2009-05-25  8:06                               ` Jens Axboe
2009-05-25  8:43                               ` Zhang, Yanmin
2009-05-25  8:48                                 ` Jens Axboe
2009-05-25  8:54                         ` Zhang, Yanmin
2009-05-25  8:54                           ` Zhang, Yanmin
2009-05-22  7:53                     ` Jens Axboe
2009-05-22  7:53                       ` Jens Axboe
2009-05-25 15:57 ` Richard Kennedy
2009-05-25 17:05   ` Jens Axboe

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=20090520092528.GP11363@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yanmin_zhang@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.