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: <20170622154336.5ry5lzhw3yv27u4q@thunk.org> Date: Thu, 22 Jun 2017 11:43:36 -0400 From: Theodore Ts'o <tytso@....edu> To: Tahsin Erdogan <tahsin@...gle.com> Cc: Andreas Dilger <adilger@...ger.ca>, "Darrick J . Wong" <darrick.wong@...cle.com>, Jan Kara <jack@...e.cz>, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 26/32] ext4: cleanup transaction restarts during inode deletion On Wed, Jun 21, 2017 at 06:49:33PM -0700, Tahsin Erdogan wrote: > During inode deletion, journal credits that will be needed are hard to > determine, that is why we have journal extend/restart calls in several > places. Whenever a transaction is restarted, filesystem must be in a > consistent state because there is no atomicity guarantee beyond a > restart call. > > Add ext4_xattr_ensure_credits() helper function which takes care of > journal extend/restart logic. It also handles getting jbd2 write access > and dirty metadata calls. This function is called at every iteration of > handling an ea_inode reference. > > Signed-off-by: Tahsin Erdogan <tahsin@...gle.com> Applied, thanks. - Ted
Powered by blists - more mailing lists