| 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: Wed, 18 Nov 2009 16:05:48 +0800 From: Li Yang <leoli@...escale.com> To: linux-kernel@...r.kernel.org Cc: akpm@...ux-foundation.org, gregkh@...e.de, Li Yang <leoli@...escale.com> Subject: [RFC] char/mem: Honor O_SYNC over intelligent setting of uncached access The original code will automatially set the page non-cacheable if the mmap'ped address is not in kernel managed low memory. We already have O_SYNC flag to pass the cacheability settings. Therefore we should honor the case that O_SYNC is delibrately not used. For example, it is useful to the case that not all system memory is managed by Linux, and want to be mmaped cacheable. Not sure if there is anything out there depending on the previous behavior. Signed-off-by: Li Yang <leoli@...escale.com> --- drivers/char/mem.c | 8 +++----- 1 files changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/char/mem.c b/drivers/char/mem.c index a074fce..34a9b24 100644 --- a/drivers/char/mem.c +++ b/drivers/char/mem.c @@ -56,12 +56,10 @@ static inline int uncached_access(struct file *file, unsigned long addr) } #else /* - * Accessing memory above the top the kernel knows about or through a file pointer - * that was marked O_SYNC will be done non-cached. + * Accessing memory through a file pointer that was marked O_SYNC will be done + * non-cached. */ - if (file->f_flags & O_SYNC) - return 1; - return addr >= __pa(high_memory); + return (file->f_flags & O_SYNC) ? 1 : 0; #endif } -- 1.6.3.1.6.g4bf1f -- 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