Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAOH5QeChR8s6vENfRdGtUeeqKsSSbeFkY9TArmOyDcUvgAgU7Q@mail.gmail.com>
 <CAOH5QeC0PhnZY6Cpe4zZ8o07XHA4-5B3xGEontkezrYu=Jt0VQ@mail.gmail.com> <7074179d.c3fd.17aa3f148cc.Coremail.wuzhouhui14@mails.ucas.ac.cn>
In-Reply-To: <7074179d.c3fd.17aa3f148cc.Coremail.wuzhouhui14@mails.ucas.ac.cn>
From:   yong w <yongw.pur@gmail.com>
Date:   Wed, 14 Jul 2021 22:30:22 +0800
Message-ID: <CAOH5QeCV3c-=RiwGrUn7214NRZye7wYFmPSyFWxw-0Zvk=j2GQ@mail.gmail.com>
Subject: Re: Re: [BUG] ramfs system panic when using dd to create files
To:     wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Cc:     linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        akpm@linux-foundation.org, nico@fluxnic.net, wang.yong12@zte.com.cn
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Thanks for your reply!

> Limit max size of ramfs.
It's no use using size to limit the size of ramfs.
"mount -t ramfs -o size=10M ramfs /ramfs" is the command i use.

>
> The comments already explains why kernel should panic on this situation:
>             /*
>              * If we got here due to an actual allocation at the
>              * system level, we cannot survive this and will enter
>              * an endless loop in the allocator. Bail out now.
>              */
But it causes panic, actually , I don't want it panics