diff for duplicates of <1316357705-sup-2667@shiny> diff --git a/a/1.txt b/N1/1.txt index 61fb9d2..35245b4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,38 +1,32 @@ Excerpts from Jeff liu's message of 2011-09-18 06:33:38 -0400: ->=20 -> =E5=9C=A8 2011-9-18=EF=BC=8C=E4=B8=8B=E5=8D=884:42=EF=BC=8C Marco Sto= -rnelli =E5=86=99=E9=81=93=EF=BC=9A ->=20 +> +> 在 2011-9-18，下午4:42， Marco Stornelli 写道： +> > > Il 18/09/2011 09:29, Jeff Liu ha scritto: > >> Hi Andreas and Andi, -> >>=20 +> >> > >> Thanks for your comments. -> >>=20 +> >> > >> On 09/18/2011 09:46 AM, Andi Kleen wrote: -> >>=20 -> >>>>> with an additional improvement if the offset is larger or equal= - to the +> >> +> >>>>> with an additional improvement if the offset is larger or equal to the > >>>>> file size, return -ENXIO in directly: -> >>>>>=20 -> >>>>> if (offset>=3D inode->i_size) { +> >>>>> +> >>>>> if (offset>= inode->i_size) { > >>>>> mutex_unlock(&inode->i_mutex); > >>>>> return -ENXIO; > >>>>> } -> >>>>=20 -> >>>> Except that is wrong, because it would then be impossible to wri= -te sparse files. -> >>=20 -> >> Per my tryout, except that, if the offset>=3D source file size, ca= -ll -> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always r= -eturn -> >> the total file size rather than -ENXIO. however, our desired resu= -lt it +> >>>> +> >>>> Except that is wrong, because it would then be impossible to write sparse files. +> >> +> >> Per my tryout, except that, if the offset>= source file size, call +> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always return +> >> the total file size rather than -ENXIO. however, our desired result it > >> -ENXIO in this case, Am I right? -> >>=20 -> >=20 +> >> +> > > > Yes, ENXIO should be the operation result. ->=20 +> > Thanks for your kind confirmation. Thanks everyone, I've put Jeff's last version of this in my queue. diff --git a/a/content_digest b/N1/content_digest index 46ac02e..5c83e64 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -23,44 +23,38 @@ "\00:1\0" "b\0" "Excerpts from Jeff liu's message of 2011-09-18 06:33:38 -0400:\n" - ">=20\n" - "> =E5=9C=A8 2011-9-18=EF=BC=8C=E4=B8=8B=E5=8D=884:42=EF=BC=8C Marco Sto=\n" - "rnelli =E5=86=99=E9=81=93=EF=BC=9A\n" - ">=20\n" + "> \n" + "> \345\234\250 2011-9-18\357\274\214\344\270\213\345\215\2104:42\357\274\214 Marco Stornelli \345\206\231\351\201\223\357\274\232\n" + "> \n" "> > Il 18/09/2011 09:29, Jeff Liu ha scritto:\n" "> >> Hi Andreas and Andi,\n" - "> >>=20\n" + "> >> \n" "> >> Thanks for your comments.\n" - "> >>=20\n" + "> >> \n" "> >> On 09/18/2011 09:46 AM, Andi Kleen wrote:\n" - "> >>=20\n" - "> >>>>> with an additional improvement if the offset is larger or equal=\n" - " to the\n" + "> >> \n" + "> >>>>> with an additional improvement if the offset is larger or equal to the\n" "> >>>>> file size, return -ENXIO in directly:\n" - "> >>>>>=20\n" - "> >>>>> if (offset>=3D inode->i_size) {\n" + "> >>>>> \n" + "> >>>>> if (offset>= inode->i_size) {\n" "> >>>>> mutex_unlock(&inode->i_mutex);\n" "> >>>>> return -ENXIO;\n" "> >>>>> }\n" - "> >>>>=20\n" - "> >>>> Except that is wrong, because it would then be impossible to wri=\n" - "te sparse files.\n" - "> >>=20\n" - "> >> Per my tryout, except that, if the offset>=3D source file size, ca=\n" - "ll\n" - "> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always r=\n" - "eturn\n" - "> >> the total file size rather than -ENXIO. however, our desired resu=\n" - "lt it\n" + "> >>>> \n" + "> >>>> Except that is wrong, because it would then be impossible to write sparse files.\n" + "> >> \n" + "> >> Per my tryout, except that, if the offset>= source file size, call\n" + "> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always return\n" + "> >> the total file size rather than -ENXIO. however, our desired result it\n" "> >> -ENXIO in this case, Am I right?\n" - "> >>=20\n" - "> >=20\n" + "> >> \n" + "> > \n" "> > Yes, ENXIO should be the operation result.\n" - ">=20\n" + "> \n" "> Thanks for your kind confirmation.\n" "\n" "Thanks everyone, I've put Jeff's last version of this in my queue.\n" "\n" -chris -476d9c3f03c411d890c83c3e245476195de644e882e7667c6bb5751c2b423587 +58d19ac4f287d34bddc48bf4667d97bcddd88203b1a7b1813fa72dc3328aa234
diff --git a/a/1.txt b/N2/1.txt index 61fb9d2..e013abe 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,38 +1,32 @@ Excerpts from Jeff liu's message of 2011-09-18 06:33:38 -0400: ->=20 -> =E5=9C=A8 2011-9-18=EF=BC=8C=E4=B8=8B=E5=8D=884:42=EF=BC=8C Marco Sto= -rnelli =E5=86=99=E9=81=93=EF=BC=9A ->=20 +> +> 在 2011-9-18，下åˆ4:42， Marco Stornelli 写é“： +> > > Il 18/09/2011 09:29, Jeff Liu ha scritto: > >> Hi Andreas and Andi, -> >>=20 +> >> > >> Thanks for your comments. -> >>=20 +> >> > >> On 09/18/2011 09:46 AM, Andi Kleen wrote: -> >>=20 -> >>>>> with an additional improvement if the offset is larger or equal= - to the +> >> +> >>>>> with an additional improvement if the offset is larger or equal to the > >>>>> file size, return -ENXIO in directly: -> >>>>>=20 -> >>>>> if (offset>=3D inode->i_size) { +> >>>>> +> >>>>> if (offset>= inode->i_size) { > >>>>> mutex_unlock(&inode->i_mutex); > >>>>> return -ENXIO; > >>>>> } -> >>>>=20 -> >>>> Except that is wrong, because it would then be impossible to wri= -te sparse files. -> >>=20 -> >> Per my tryout, except that, if the offset>=3D source file size, ca= -ll -> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always r= -eturn -> >> the total file size rather than -ENXIO. however, our desired resu= -lt it +> >>>> +> >>>> Except that is wrong, because it would then be impossible to write sparse files. +> >> +> >> Per my tryout, except that, if the offset>= source file size, call +> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always return +> >> the total file size rather than -ENXIO. however, our desired result it > >> -ENXIO in this case, Am I right? -> >>=20 -> >=20 +> >> +> > > > Yes, ENXIO should be the operation result. ->=20 +> > Thanks for your kind confirmation. Thanks everyone, I've put Jeff's last version of this in my queue. diff --git a/a/content_digest b/N2/content_digest index 46ac02e..a520cb9 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -23,44 +23,38 @@ "\00:1\0" "b\0" "Excerpts from Jeff liu's message of 2011-09-18 06:33:38 -0400:\n" - ">=20\n" - "> =E5=9C=A8 2011-9-18=EF=BC=8C=E4=B8=8B=E5=8D=884:42=EF=BC=8C Marco Sto=\n" - "rnelli =E5=86=99=E9=81=93=EF=BC=9A\n" - ">=20\n" + "> \n" + "> \303\245\302\234\302\250 2011-9-18\303\257\302\274\302\214\303\244\302\270\302\213\303\245\302\215\302\2104:42\303\257\302\274\302\214 Marco Stornelli \303\245\302\206\302\231\303\251\302\201\302\223\303\257\302\274\302\232\n" + "> \n" "> > Il 18/09/2011 09:29, Jeff Liu ha scritto:\n" "> >> Hi Andreas and Andi,\n" - "> >>=20\n" + "> >> \n" "> >> Thanks for your comments.\n" - "> >>=20\n" + "> >> \n" "> >> On 09/18/2011 09:46 AM, Andi Kleen wrote:\n" - "> >>=20\n" - "> >>>>> with an additional improvement if the offset is larger or equal=\n" - " to the\n" + "> >> \n" + "> >>>>> with an additional improvement if the offset is larger or equal to the\n" "> >>>>> file size, return -ENXIO in directly:\n" - "> >>>>>=20\n" - "> >>>>> if (offset>=3D inode->i_size) {\n" + "> >>>>> \n" + "> >>>>> if (offset>= inode->i_size) {\n" "> >>>>> mutex_unlock(&inode->i_mutex);\n" "> >>>>> return -ENXIO;\n" "> >>>>> }\n" - "> >>>>=20\n" - "> >>>> Except that is wrong, because it would then be impossible to wri=\n" - "te sparse files.\n" - "> >>=20\n" - "> >> Per my tryout, except that, if the offset>=3D source file size, ca=\n" - "ll\n" - "> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always r=\n" - "eturn\n" - "> >> the total file size rather than -ENXIO. however, our desired resu=\n" - "lt it\n" + "> >>>> \n" + "> >>>> Except that is wrong, because it would then be impossible to write sparse files.\n" + "> >> \n" + "> >> Per my tryout, except that, if the offset>= source file size, call\n" + "> >> lseek(fd, offset, SEEK_DATA/SEEK_HOLE) against Btrfs will always return\n" + "> >> the total file size rather than -ENXIO. however, our desired result it\n" "> >> -ENXIO in this case, Am I right?\n" - "> >>=20\n" - "> >=20\n" + "> >> \n" + "> > \n" "> > Yes, ENXIO should be the operation result.\n" - ">=20\n" + "> \n" "> Thanks for your kind confirmation.\n" "\n" "Thanks everyone, I've put Jeff's last version of this in my queue.\n" "\n" -chris -476d9c3f03c411d890c83c3e245476195de644e882e7667c6bb5751c2b423587 +d62376f1c08d8083ea67d6e356a046c2b8416f3788475c774595899acb52207d
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.