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: Fri, 24 Jun 2011 16:41:43 +0800 From: Yongqiang Yang <xiaoqiangnk@...il.com> To: adilger@...ger.ca Cc: Ext4 Developers List <linux-ext4@...r.kernel.org> Subject: Do we really need parallel resizer? Hi Andreas, I noticed that resize is protected by resize_lock. Then parallel resizer works. However, I think there is no need to make parallel resizer work. I think we can use an atomic integer 'resize_flag' instead of resize_lock, resize_flag is set to 1 before the kernel does resizing work, while resize_flag is set to 0 after the kernel finishes resizing work. Resizing is allowed only if resize_flag is 0. If resize_flag is 1, kernel returns -EBUSY to userspace. What about your opinion? Yongqiang. -- Best Wishes Yongqiang Yang -- 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