From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Matthew Wilcox <willy@infradead.org>,
Erik Jensen <erikjensen@rkjnsn.net>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: page->index limitation on 32bit system?
Date: Sat, 20 Feb 2021 07:13:18 +0800 [thread overview]
Message-ID: <9ff87076-17c5-ba44-a7f4-2af31fe02144@gmx.com> (raw)
In-Reply-To: <20210219175108.GV2858050@casper.infradead.org>
On 2021/2/20 上午1:51, Matthew Wilcox wrote:
> On Fri, Feb 19, 2021 at 02:22:01PM +0000, Matthew Wilcox wrote:
>> In the last decade, nobody's tried to fix it in mainline that I know of.
>> As I said, some vendors have tried to fix it in their NAS products,
>> but I don't know where to find that patch any more.
>
> Arnd found it for me.
>
> https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/alpine-source/linux-3.10.x-bsp.txz/download
>
> They've done a perfect job of making the source available while making it
> utterly dreadful to extract anything useful from.
>
> 16084 files changed, 1322769 insertions(+), 285257 deletions(-)
Wow, I thought RedHat was the only open-source vendor that tries to send
out a super big patch to make life of every other guys miserable.
And I'm definitely wrong now.
>
> It's full of gratuitous whitespace changes to files that definitely
> aren't used (arch/alpha? really?) and they've stripped out a lot of
> comments that they didn't need to touch.
>
> Forward porting a patch from 10 years ago wouldn't be easy, even if
> they hadn't tried very hard to obfuscate their patch. I don't think
> this will be a fruitful line of inquiry.
>
Yeah, I believe it's not worthy now.
I'll make btrfs to try its best to reject the fs instead.
Thanks,
Qu
next prev parent reply other threads:[~2021-02-19 23:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 8:54 page->index limitation on 32bit system? Qu Wenruo
2021-02-18 12:15 ` Matthew Wilcox
2021-02-18 12:42 ` Qu Wenruo
2021-02-18 13:39 ` Matthew Wilcox
2021-02-19 0:37 ` Qu Wenruo
2021-02-19 16:12 ` Theodore Ts'o
2021-02-19 23:10 ` Qu Wenruo
2021-02-20 0:23 ` Matthew Wilcox
2021-02-22 0:19 ` Dave Chinner
2021-02-20 2:20 ` Erik Jensen
2021-02-20 3:40 ` Matthew Wilcox
2021-02-20 23:02 ` Erik Jensen
2021-02-20 23:22 ` Matthew Wilcox
2021-02-21 0:01 ` Erik Jensen
2021-02-21 17:15 ` Matthew Wilcox
2021-02-18 21:27 ` Erik Jensen
2021-02-19 14:22 ` Matthew Wilcox
2021-02-19 17:51 ` Matthew Wilcox
2021-02-19 23:13 ` Qu Wenruo [this message]
2021-02-22 1:48 ` Dave Chinner
2021-03-01 1:49 ` GWB
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=9ff87076-17c5-ba44-a7f4-2af31fe02144@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=erikjensen@rkjnsn.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
/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