| 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: <20080603153304.741eaa2b.akpm@linux-foundation.org> Date: Tue, 3 Jun 2008 15:33:04 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> Cc: sct@...hat.com, adilger@...sterfs.com, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, jack@...e.cz, jbacik@...hat.com, cmm@...ibm.com, tytso@....edu, yumiko.sugita.yf@...achi.com, satoshi.oshima.fk@...achi.com Subject: Re: [PATCH 2/5] jbd: ordered data integrity fix On Mon, 02 Jun 2008 19:45:04 +0900 Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> wrote: > In ordered mode, if a buffer being dirtied exists in the committing I changed this text to read "if a file data buffer being dirtied". Please do be careful when describing all these buffers, else it gets more confusing that it already is. > transaction, we write the buffer to the disk, move it from the > committing transaction to the running transaction, then dirty it. > But we don't have to remove the buffer from the committing > transaction when the buffer couldn't be written out, otherwise it > would miss the error and the committing transaction would not abort. > > This patch adds an error check before removing the buffer from the > committing transaction. -- 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