Re: [PATCH 03/18] f2fs crypto: declare some definitions for f2fs encryption feature

2015-05-16 Thread Tom Marshall
On Sat, May 16, 2015 at 09:24:03AM -0400, Theodore Ts'o wrote: > [...] What's going to be more difficult in the long run is > when we want to support per-block data integrity, using (for example) > AES/GCM, which will require 32 bytes of per-block "authentication tag" > (think Message Authenticatio

Re: [PATCH 03/18] f2fs crypto: declare some definitions for f2fs encryption feature

2015-05-15 Thread Tom Marshall
On Fri, May 15, 2015 at 06:14:24PM -0700, Jaegeuk Kim wrote: > On Thu, May 14, 2015 at 09:50:44AM -0700, Tom Marshall wrote: > > Please keep in mind that I'm also working on transparent > > compression. I'm watching this thread closely so that I can > > implement

Re: [PATCH 03/18] f2fs crypto: declare some definitions for f2fs encryption feature

2015-05-14 Thread Tom Marshall
Please keep in mind that I'm also working on transparent compression. I'm watching this thread closely so that I can implement a compression library alongside the crypto library. If there is any interest or benefit, I would be glad to work together so that the two can be done cooperatively at

Re: itimer oddness in 2.6.12

2005-07-22 Thread Tom Marshall
On Fri, Jul 22, 2005 at 08:21:25PM +0100, Paulo Marques wrote: > Tom Marshall wrote: > >The patch to fix "setitimer timer expires too early" is causing issues for > >the Helix server. We have a timer processs that updates the server's > >timestamp on an it

itimer oddness in 2.6.12

2005-07-22 Thread Tom Marshall
The patch to fix "setitimer timer expires too early" is causing issues for the Helix server. We have a timer processs that updates the server's timestamp on an itimer and it expects the signal to be delivered at roughly the interval retrieved from getitimer. This is very consistent on every platf