linux-kernel - Re: [GIT PULL] a few writeback fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Sep 2009 18:42:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>, jack@...e.cz,
	fengguang.wu@...el.com
Subject: Re: [GIT PULL] a few writeback fixes


* Jens Axboe <jens.axboe@...cle.com> wrote:

> Hi Linus,
> 
> This fixes a problem with NFS killing its bdi without being 
> initialized, and also contains a fix for a busy loop (where we forgot 
> to set the task state before sleeping). Since these are a bit critical 
> for -rc1, I'm pushing them out before leaving for Portland.
> 
> Jan, since we're not really sure on the inode wait yet, I dropped that 
> patch. It's definitely something to look into, as are the congestion 
> bits.
> 
> I plan on adding some writeback tracing code while on the plane for 
> further analysis when I get back.
> 
>   git://git.kernel.dk/linux-2.6-block.git writeback
> 
> Jens Axboe (4):
>       nfs: nfs_kill_super() should call bdi_unregister() after killing super
>       writeback: don't use schedule_timeout() without setting runstate
>       writeback: make balance_dirty_pages() gradually back more off
>       nfs: initialize the backing_dev_info when creating the server
> 
>  fs/nfs/client.c     |   10 ++++++----
>  fs/nfs/super.c      |    2 +-
>  mm/page-writeback.c |   11 ++++++++++-
>  3 files changed, 17 insertions(+), 6 deletions(-)

just an update about the BDI slab corruption bugs i reported in this 
thread on lkml:

   [origin tree SLAB corruption] BUG kmalloc-64: Poison overwritten,
        INFO: Allocated in bdi_alloc_work+0x2b/0x100 age=175 cpu=1 pid=3514

They have gone away entirely with your earlier BDI fixes/updates, on all 
-tip testsystems that triggered it. So that bug can be closed for good.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/