lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 16 Mar 2021 14:01:04 +0100
From:   Michal Hocko <>
To:     Al Viro <>
Cc:     Greg Kroah-Hartman <>,
        Kees Cook <>,
        Andrew Morton <>,
        Alexey Dobriyan <>,
        Lee Duncan <>, Chris Leech <>,
        Adam Nichols <>,,,
Subject: Re: [PATCH v2] seq_file: Unconditionally use vmalloc for buffer

On Tue 16-03-21 12:43:12, Al Viro wrote:
> AFAICS, Kees wants to protect against ->show() instances stomping beyond
> the page size.  What I don't get is what do you get from using seq_file
> if you insist on doing raw access to the buffer rather than using
> seq_printf() and friends.  What's the point?

I do not think there is any and as you have said in other response we
should really make seq_get_buf internal thing to seq_file and be done
with that. If there is a missing functionality that users workaround by
abusing seq_get_buf then it should be added into seq_file interface.
Michal Hocko

Powered by blists - more mailing lists