From: Eric Sandeen <sandeen@redhat.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Eric Paris <eparis@redhat.com>,
linux-ext4@vger.kernel.org, selinux@tycho.nsa.gov,
sds@tycho.nsa.gov, esandeen@redhat.com, tytso@mit.edu,
dwalsh@redhat.com, linux-security-module@vger.kernel.org
Subject: Re: ext4_has_free_blocks always checks cap_sys_resource and makes SELinux unhappy
Date: Fri, 24 Oct 2008 14:02:44 -0500 [thread overview]
Message-ID: <49021BD4.2040305@redhat.com> (raw)
In-Reply-To: <1224874836.6379.3.camel@mingming-laptop>
Mingming Cao wrote:
> Most functionality in ext4_has_free_blocks() is duplicated in
> ext4_claim_free_blocks(). I guess the ext4_has_free_blocks() could be
> simplified a bit, or the two functional merge into one.
>
> The delay cap check sounds right thing to me.
good point on the duplication, I'll merge them as part of this.
Thanks Mingming,
-Eric
next prev parent reply other threads:[~2008-10-24 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 15:05 ext4_has_free_blocks always checks cap_sys_resource and makes SELinux unhappy Eric Paris
2008-10-24 15:05 ` Eric Paris
2008-10-24 15:08 ` Stephen Smalley
2008-10-24 15:08 ` Stephen Smalley
2008-10-24 17:28 ` Eric Paris
2008-10-24 17:28 ` Eric Paris
2008-10-24 17:38 ` Stephen Smalley
2008-10-24 17:38 ` Stephen Smalley
2008-10-24 16:56 ` Eric Sandeen
2008-10-24 19:00 ` Mingming Cao
2008-10-24 19:02 ` Eric Sandeen [this message]
2008-10-27 1:39 ` Eric Sandeen
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=49021BD4.2040305@redhat.com \
--to=sandeen@redhat.com \
--cc=cmm@us.ibm.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=esandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.