linux-ext4 - Re: A proposal for making ext4's journal more SMR (and flash) friendly

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140108233752.GD17750@thunk.org>
Date:	Wed, 8 Jan 2014 18:37:52 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: A proposal for making ext4's journal more SMR (and flash)
 friendly

On Wed, Jan 08, 2014 at 11:14:30PM +0100, Jan Kara wrote:
>   So when I was thinking about this (already couple of years ago) the thing
> which stopped me was the question at which layer we should do the
> translation. Ideally we would need something at submit_bh() level but just
> wrapping submit_bh() calls inside ext4 isn't enough for stuff like symlinks
> or journalled data... Do you have any thoughts on that?

I think there are two interfaces that should handle nearly all of our
journal block mapping needs.  The functions that issue bio requests
directly tend to use ext4_get_block*() functions, and functions which
use the buffer cache uses submit_bh() (typically via ext4_getblk).
There will probably be a few exceptions, but I don't think this should
be an intractable problem.

Regards,

					- 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