LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sami Farin <7atbggg02@sneakemail.com>
To: David Chinner <dgc@sgi.com>
Cc: Adrian Bunk <bunk@stusta.de>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs-masters@oss.sgi.com
Subject: Re: 2.6.20-rc5: known unfixed regressions
Date: Fri, 19 Jan 2007 00:55:00 +0200 [thread overview]
Message-ID: <20070118225500.GC16110@m.safari.iki.fi> (raw)
In-Reply-To: <20070117034329.GW44411608@melbourne.sgi.com>
On Wed, Jan 17, 2007 at 14:43:29 +1100, David Chinner wrote:
...
> > > Subject : BUG: at mm/truncate.c:60 cancel_dirty_page() (XFS)
> > > References : http://lkml.org/lkml/2007/1/5/308
> > > Submitter : Sami Farin <7atbggg02@sneakemail.com>
> > > Handled-By : David Chinner <dgc@sgi.com>
> > > Status : problem is being discussed
> >
> > I'm at LCA and been having laptop dramas so the fix is being held up at this
> > point. I and trying to test a change right now that adds an optional unmap
> > to truncate_inode_pages_range as XFS needs, in some circumstances, to toss
> > out dirty pages (with dirty bufferheads) and hence requires truncate semantics
> > that are currently missing unmap calls.
> >
> > Semi-untested patch attached below.
>
> The patch has run XFSQA for about 24 hours now on my test rig without
> triggering any problems.
I have also ran this for 24h (in patched 2.6.19.2)
and no problems noticed :)
--
Do what you love because life is too short for anything else.
next prev parent reply other threads:[~2007-01-18 22:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 19:27 Linux v2.6.20-rc5 Linus Torvalds
2007-01-12 22:26 ` Andrew Morton
2007-01-13 2:26 ` Nigel Cunningham
2007-01-13 3:36 ` Jeff Chua
2007-01-13 3:44 ` Jeff Chua
2007-01-13 20:23 ` Bill Davidsen
2007-01-13 23:58 ` Segher Boessenkool
2007-01-13 5:01 ` Adrian Bunk
2007-01-13 13:02 ` Jan Engelhardt
2007-01-14 7:38 ` Jeff Chua
2007-01-14 7:43 ` Adrian Bunk
2007-01-13 7:11 ` 2.6.20-rc5: known unfixed regressions Adrian Bunk
2007-01-13 15:51 ` Damien Wyart
2007-01-13 15:59 ` Adrian Bunk
2007-01-13 16:38 ` Jon Smirl
2007-01-13 20:55 ` Aaron Sethman
2007-01-14 12:09 ` Ingo Molnar
2007-01-16 6:15 ` David Chinner
2007-01-17 3:43 ` David Chinner
2007-01-18 22:55 ` Sami Farin [this message]
2007-01-13 7:14 ` 2.6.20-rc5: known regressions with patches Adrian Bunk
2007-01-13 15:32 ` Roland Dreier
2007-01-13 16:21 ` Adrian Bunk
2007-01-18 19:47 ` 2.6.20-rc5: knwon unfixed regressions (v2) (part1) Adrian Bunk
2007-01-18 19:54 ` 2.6.20-rc5: knwon unfixed regressions (v2) (part2) Adrian Bunk
2007-01-18 19:59 ` 2.6.20-rc5: known regressions with patches (v2) Adrian Bunk
2007-01-19 1:43 ` David Woodhouse
2007-01-24 15:46 ` 2.6.20-rc5: known unfixed regressions (v3) (part 1) Adrian Bunk
2007-01-24 15:47 ` 2.6.20-rc5: known unfixed regressions (v3) (part 2) Adrian Bunk
2007-01-24 16:06 ` Lennart Sorensen
2007-01-24 16:38 ` Adrian Bunk
2007-01-24 16:57 ` Lennart Sorensen
2007-01-24 20:06 ` Adrian Bunk
2007-01-24 20:45 ` Peter Osterlund
2007-01-25 15:32 ` Gerhard Dirschl
2007-01-26 11:13 ` Andrew Clayton
2007-01-24 15:50 ` 2.6.20-rc5: known regressions with patches (v3) Adrian Bunk
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=20070118225500.GC16110@m.safari.iki.fi \
--to=7atbggg02@sneakemail.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=xfs-masters@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;
as well as URLs for NNTP newsgroup(s).