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: <20120424015323.GC18865@thunk.org> Date: Mon, 23 Apr 2012 21:53:23 -0400 From: Ted Ts'o <tytso@....edu> To: Shaohua Li <shli@...nel.org> Cc: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [RFC]jbd2: use GFP_NOFS for blkdev_issue_flush On Fri, Apr 13, 2012 at 10:27:35AM +0800, Shaohua Li wrote: > > flush request is issued in transaction commit code path, so looks using > GFP_KERNEL to allocate memory for flush request bio falls into the classic > deadlock issue. I saw btrfs and dm get it right, but ext4, xfs and md are > using GFP_KERNEL, which makes me confused. Hoping filesystem developers > clarify. > > Signed-off-by: Shaohua Li <shli@...ionio.com> Thanks, applied. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists