From: Andrew Morton on 7 Jul 2010 17:20 On Wed, 7 Jul 2010 23:02:09 +0200 Christoph Hellwig <hch(a)lst.de> wrote: > On Wed, Jul 07, 2010 at 01:51:18PM -0700, Andrew Morton wrote: > > There have been various dramas in the writeback code recently. > > Christoph has been working on it. > > > > Christoph, is this oops known about, and are those patches expected to > > fix it? > > I have no idea what oops you mean. http://lmgtfy.com/?q=fs%2Ffs-writeback+oopses+in+kernel+2.6.33.4-95.fc13.i686.PAE > But the writeback code is very > different now compared to 2.6.33, and with the latest fixes in Jens' > tree there are no known issues left. (know to me anyway) Well the issue is that 2.6.33.x goes oops and we'd like to fix that. if it's fixed in current mainline then which patch did it? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Christoph Hellwig on 7 Jul 2010 18:40 On Wed, Jul 07, 2010 at 02:14:31PM -0700, Andrew Morton wrote: > > > > I have no idea what oops you mean. > > http://lmgtfy.com/?q=fs%2Ffs-writeback+oopses+in+kernel+2.6.33.4-95.fc13.i686.PAE Not particularly useful. Line numbers and function have changed completely since .33. Given that 2.6.33-stable is at the end of line I really can't be bothered to go back, figure out what the hell was going on back then and backport things. In fact we'd probably end up backporting all writeback changes since then anyway, as the changes to sort out the per-sb syncs were very large and interdependent. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
First
|
Prev
|
Pages: 1 2 3 Prev: [PATCH] md: fix raid6test build error Next: [PATCH] x86/mm: remove unused DBG() macro |