| 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
| ||
|
Message-ID: <CAGEw7Sq4FRPOvzjcP5_NRFp-xkRaGp8EPBZYhqdS+utJN2PC4w@mail.gmail.com> Date: Tue, 26 May 2015 22:17:00 +0800 From: 曾昭荣 <zrzeng@...il.com> To: linux-fsdevel@...r.kernel.org Cc: linux-kernel@...r.kernel.org Subject: Close all file descriptors for a process before starting its core dump? Hi VFS and kernel experts, I'd like to ask help about whether kernel can close all file descriptors for a process just before starting this process's core dump? We have an application that uses large amount of memory (80G). When it panic and core dump, it will need a long time to save the core file. During which, file locks held by this application will block other processes accessing this file for a long time, this causes bad end-user experience I have a kernel customization which closes all file descriptors for this process just before starting its core dump. This way any file locks held by this process can be released automatically inside kernel before core dump. I am wondering whether this kernel customization can cause any side effects for the user land process memory state? I roughly went through mmap/socket/fifo/ pipe/sysv-ipc code, it looks closing files from inside kernel doesn't change user land process's memory content. However I am not sure, so I would like to ask help and confirm from you. Thanks a lot! Jason -- 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