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
| ||
|
Date: Sun, 16 Nov 2008 01:11:04 +0100 From: Bernhard Walle <bwalle@...e.de> To: Bernhard Walle <bwalle@...e.de> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [PATCH 2/2] Add dev.mem.restricted sysctl * Bernhard Walle [2008-11-16 01:03]: > > + > +static const struct trans_ctl_table trans_mem_table[] = { > + { DEV_MEM_RESTRICTED, "restricted" }, > + {} > +}; Noticed that we either need to put everything into CONFIG_STRICT_DEVMEM or nothing. But I want to head opinions if the concept can be accepted before I repost. Regards, Bernhard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists