public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: linux-ext4@vger.kernel.org
Cc: dvhart@linux.intel.com, tytso@mit.edu, darrick.wong@oracle.com,
	liezhi.yang@windriver.com
Subject: [PATCH] misc: copy extended attributes in populate_fs
Date: Fri, 27 Jun 2014 22:02:16 +0100	[thread overview]
Message-ID: <1403902937-2781-1-git-send-email-ross.burton@intel.com> (raw)

Hi,

When using mkefs with -d to create a file system image from a pre-constructed
root filesystem directory, any extended attributes set are not copied into the
filesystem.

This is a problem when the file system needs them, for example it uses SELinux.
Following is a patch to copy any extended attributes to the target file system
in populate_fs().

Regards,
Ross

             reply	other threads:[~2014-06-27 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 21:02 Ross Burton [this message]
2014-06-27 21:02 ` [PATCH] misc: copy extended attributes in populate_fs Ross Burton
2014-06-30 18:43   ` Darrick J. Wong
2014-06-30 18:59     ` Burton, Ross
2014-06-30 19:13       ` Darrick J. Wong

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=1403902937-2781-1-git-send-email-ross.burton@intel.com \
    --to=ross.burton@intel.com \
    --cc=darrick.wong@oracle.com \
    --cc=dvhart@linux.intel.com \
    --cc=liezhi.yang@windriver.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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