From: Andrew Morton <akpm@linux-foundation.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, safford@watson.ibm.com,
serue@linux.vnet.ibm.com, sailer@watson.ibm.com,
zohar@us.ibm.com, sds@tycho.nsa.gov, casey@schaufler-ca.com
Subject: Re: [RFC][Patch 5/5]integrity: IMA as an integrity service provider
Date: Thu, 29 May 2008 16:35:01 -0700 [thread overview]
Message-ID: <20080529163501.5a672b8f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1212097834.15923.7.camel@localhost.localdomain>
On Thu, 29 May 2008 17:50:34 -0400
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> On Wed, 2008-05-28 at 20:30 -0700, Andrew Morton wrote:
>
> > > ...
> > >
> > > > - All the games with mtimes should be described in the changelog too.
> > >
> > > Ok. The timespec_recent and mtime issues are part of the same problem
> > > of detecting when a file has been modified.
> >
> > Can't use inode.i_version?
>
> i_version is now working on my system.
Oh good.
> It looks good. Is
> there anything that I need to be concerned about, such as
> limited filesystem support or the i_version is not updated
> by file_close for mmaped files?
erk, I'm not an i_version person. It seems that it's only used on
directories (to patch up readdir coherency problems) so I guess I
misled you there.
There's file_struct.f_version, which is no good.
i_generation is no good either.
We've documented these things so wonderfully!
i_writecount looks good?
next prev parent reply other threads:[~2008-05-29 23:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 15:05 [RFC][Patch 5/5]integrity: IMA as an integrity service provider Mimi Zohar
2008-05-23 23:30 ` Randy Dunlap
2008-05-27 1:02 ` Mimi Zohar
2008-05-27 14:36 ` Mimi Zohar
2008-06-11 22:31 ` Randy Dunlap
2008-05-28 8:22 ` Andrew Morton
2008-05-29 3:17 ` Mimi Zohar
2008-05-29 3:30 ` Andrew Morton
2008-05-29 21:50 ` Mimi Zohar
2008-05-29 23:35 ` Andrew Morton [this message]
2008-05-30 1:58 ` Mimi Zohar
2008-05-30 2:04 ` Andrew Morton
2008-05-30 13:06 ` Mimi Zohar
2008-05-29 3:33 ` Mimi Zohar
2008-05-31 7:54 ` Pavel Machek
2008-06-24 16:28 ` david safford
2008-08-05 17:35 ` Pavel Machek
2008-06-24 16:28 ` david safford
2008-08-05 17:32 ` Pavel Machek
[not found] <20080627131946.225566613@linux.vnet.ibm.com>
2008-06-27 16:23 ` [RFC][PATCH 5/5] integrity: " Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080529163501.5a672b8f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=sailer@watson.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=serue@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
--cc=zohar@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox