From: Dave Chinner <david@fromorbit.com>
To: jinxiu su <sujinxiu@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: some questions aoout extended attribute in my development
Date: Fri, 24 Aug 2012 07:57:16 +1000 [thread overview]
Message-ID: <20120823215716.GV19235@dastard> (raw)
In-Reply-To: <CAPRu15CvOKd=1405rerOMAy7vVQGuf0fAimPP9=0CinRSNboiQ@mail.gmail.com>
On Thu, Aug 23, 2012 at 05:16:47PM +0800, jinxiu su wrote:
> Hi....I am su, a new linuxer.
>
> I am doing some development on linux security modules(LSM), and I use
> extended attribute to store the security information.
>
> But problems encountered..
>
> when the kernel module that I developed is working a long time ,the
> extended attribute of this file named /lib/ld-2.5.so lost.Exactly, it 's
> replace by zero.
>
> and in my kernel module ,there is a policy, when create a inode, the
> extended attribute will be initialized to zero. But when I check /lib/
> ld-2.5.so, the inode is not changed, exactly it's not a new inode. I am
> becoming confused....
>
> I think there must be some fatal bugs in my kernel module.But I am just
> wondering in which condition can make a file's extended attribute field
> to be replaced by zero? in which condition can make /lib/ld-2.5.so extended
> attribute to be zero?
No idea. What filesystem did this happen on, and what kernel? it
sounds like the attribute got deleted, or a system upgrade replaced
the file with a new, possibly identical version...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-08-23 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 9:16 some questions aoout extended attribute in my development jinxiu su
2012-08-23 21:57 ` Dave Chinner [this message]
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=20120823215716.GV19235@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
--cc=sujinxiu@gmail.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