linux-kernel - Re: [PATCH v6 2/8] debugfs: prevent access to removed files' private data

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CANA-60ot0U-kCerb8cF_Bd85xC7QVvmqStPdfTUtQDBrYE_SWw@mail.gmail.com>
Date:   Sun, 19 Mar 2017 18:30:33 +0200
From:   Arkady <arkady.miasnikov@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/8] debugfs: prevent access to removed files' private data

Nicolai,

Regarding the debugfs_create_file() which ignores .mmap field in the
struct file_operations. The patch is a part of the kernel 4.8 in the
Ubuntu 16.10 and breaks quite a few online code examples of mmap
drivers.

Is is acceptable to replace the debugfs_create_file() by a macro and
fail the compilation if the .mmap field is not initialized.
Alternatively debugfs_create_file() can return an error if .mmap is
not NULL.

Thank you, Arkady.