diff for duplicates of <4D3829E7.9050305@gmail.com> diff --git a/a/1.txt b/N1/1.txt index 986ba92..46ebbe4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,24 +1,20 @@ -=E4=BA=8E 2011-1-19 23:52, Chris Mason =E5=86=99=E9=81=93: +于 2011-1-19 23:52, Chris Mason 写道: > Excerpts from Josef Bacik's message of 2011-01-19 09:14:02 -0500: >> On Wed, Jan 19, 2011 at 10:08:13PM +0800, Liuwenyi wrote: ->>> In Yang Ruirui's mail, the btrfs will create a oops. This is caused= - by a +>>> In Yang Ruirui's mail, the btrfs will create a oops. This is caused by a >>> null pointer in test_range_bit() while lock the spinlock. >>> >>> So, It is necessary to add a pointer check into test_range_bit() >>> >> ->> NAK, the tree shouldn't be null coming into this function, something= - else is +>> NAK, the tree shouldn't be null coming into this function, something else is >> going wrong. What oops is this? Thanks, The mail is here http://lkml.org/lkml/2011/1/19/24 another mesg is here http://www.aei.mpg.de/~crmafra/dmesg-2.6.35.3.txt -> What was your metadata blocksize for this oops? This call should nev= -er +> What was your metadata blocksize for this oops? This call should never > happen. -It is rare and hard to reproduced. So, I update this patch, just avoid = -a=20 +It is rare and hard to reproduced. So, I update this patch, just avoid a null pointer calling. > I think there is a larger problem, probably in the IO error handling > code since the trace had io errors beforehand. diff --git a/a/content_digest b/N1/content_digest index 50d1573..5d98c6c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -17,27 +17,23 @@ " meego-kernel <meego-kernel@meego.com>\0" "\00:1\0" "b\0" - "=E4=BA=8E 2011-1-19 23:52, Chris Mason =E5=86=99=E9=81=93:\n" + "\344\272\216 2011-1-19 23:52, Chris Mason \345\206\231\351\201\223:\n" "> Excerpts from Josef Bacik's message of 2011-01-19 09:14:02 -0500:\n" ">> On Wed, Jan 19, 2011 at 10:08:13PM +0800, Liuwenyi wrote:\n" - ">>> In Yang Ruirui's mail, the btrfs will create a oops. This is caused=\n" - " by a\n" + ">>> In Yang Ruirui's mail, the btrfs will create a oops. This is caused by a\n" ">>> null pointer in test_range_bit() while lock the spinlock.\n" ">>>\n" ">>> So, It is necessary to add a pointer check into test_range_bit()\n" ">>>\n" ">>\n" - ">> NAK, the tree shouldn't be null coming into this function, something=\n" - " else is\n" + ">> NAK, the tree shouldn't be null coming into this function, something else is\n" ">> going wrong. What oops is this? Thanks,\n" "The mail is here http://lkml.org/lkml/2011/1/19/24\n" "\n" "another mesg is here http://www.aei.mpg.de/~crmafra/dmesg-2.6.35.3.txt\n" - "> What was your metadata blocksize for this oops? This call should nev=\n" - "er\n" + "> What was your metadata blocksize for this oops? This call should never\n" "> happen.\n" - "It is rare and hard to reproduced. So, I update this patch, just avoid =\n" - "a=20\n" + "It is rare and hard to reproduced. So, I update this patch, just avoid a \n" "null pointer calling.\n" "> I think there is a larger problem, probably in the IO error handling\n" "> code since the trace had io errors beforehand.\n" @@ -47,4 +43,4 @@ "Best Regards,\n" Liu Wenyi -09121368c9cc65bc91d134e9ae42a50eb8ba03b12740a0cc62020cbbbdd68d34 +54df36a087311cb4a2afb4c1738e15621e633bf06ad285b9dad9a784f9184769
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.