| 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, 5 Mar 2014 13:40:26 -0600 From: Tiratat Patana-anake <tiratatp@...icago.edu> To: linux-kernel@...r.kernel.org Subject: Problem with JDB and per-BDI writeback I have a question about JDB and per-BDI writeback on ext3 file system. I saw that in ext3_*_write_end function (e.g. ext3_ordered_write_end and ext3_journalled_write_end), the inode was added to superblock's dirty list for a writeback. For data=journal journalling, it doesn't make sense to me. Since the journal will handle the write to the real sector on disk during checkpointing. What am I missing here? Thank you for your help. My name is Tiratat. I'm a PhD student from University of Chicago. I'm working on a project that will try to do selective journaling for random writes. Best Regards Tiratat -- Tiratat (Knot) Patana-anake ถิรธัช (น้อต) พัฒนะเอนก -- 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