mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Chen Wandun <chenwandun@huawei.com>,
	jslaby@suse.com, gregkh@linuxfoundation.org,
	daniel.vetter@ffwll.ch, sam@ravnborg.org,
	b.zolnierkie@samsung.com, lukas@wunner.de, ghalat@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] vt: fix a warning when kmalloc alloc large memory
Date: Sat, 28 Mar 2020 04:12:57 +0100	[thread overview]
Message-ID: <20200328031257.GA30454@angband.pl> (raw)
In-Reply-To: <nycvar.YSQ.7.76.2003272232340.2671@knanqh.ubzr>

On Fri, Mar 27, 2020 at 10:55:14PM -0400, Nicolas Pitre wrote:
> On Sat, 28 Mar 2020, Chen Wandun wrote:
> 
> > If the memory size that use kmalloc() to allocate exceed MAX_ORDER pages,
> > it will hit the WARN_ON_ONCE(!(gfp_mask & __GFP_NOWARN)), so add memory
> > allocation flag __GFP_NOWARN to silence a warning, othervise, it will
> > cause panic if panic_on_warn is enable.
> 
> Wow! How do you manage that? You need something like a 1024x1024 text 
> screen to get such a big memory allocation.

ioctl(VT_RESIZE) allows up to 32767x32767, unprivileged for a local user.
That's 4GB per console.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀                                       -- <willmore> on #linux-sunxi
⠈⠳⣄⠀⠀⠀⠀

  reply	other threads:[~2020-03-28  3:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28  2:13 Chen Wandun
2020-03-28  2:55 ` Nicolas Pitre
2020-03-28  3:12   ` Adam Borowski [this message]
2020-03-28 16:20     ` Nicolas Pitre
2020-03-28 20:50     ` Nicolas Pitre

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=20200328031257.GA30454@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=b.zolnierkie@samsung.com \
    --cc=chenwandun@huawei.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=ghalat@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=nico@fluxnic.net \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®