frm_notify_policyload_pre(void)
{
write_lock_bh(&xfrm_policy_lock);
flow_cache_genid++;
flow_cache_ignore = 1;
write_unlock_bh(&xfrm_policy_lock);
}
void selinux_xfrm_notify_policyload_post(void)
{
write_lock_bh(&xfrm_policy_lock);
flow_cac
t;, possibly with
"dm-userspace" patched into the kernel to allow you to handle
non-mapped blocks in your userspace daemon when somebody tries to
access them. If you don't need that ability then straight dm-loop and
dm-linear will work.
Cheers,
Kyle Moffett
--
To unsubscribe from
one related bug-fix^Wdirty hack
for sky2 to reset the PHY a second time during netif-up after enabling
interrupts; otherwise the immediate "link up" interrupt gets lost.
Once I get approval from the company I will patch the post itself for
review.
I look forward to your comments and su
yright ownership over this code then there are a
great many other people you must contact and convince first.
I would encourage you to talk privately with the Software Freedom
Conservancy before sending more patches of this nature.
Cheers,
Kyle Moffett
> diff --git a/drivers/target/target_co
rm_policy_lock);
}
void selinux_xfrm_notify_policyload_post(void)
{
write_lock_bh(&xfrm_policy_lock);
flow_cache_ignore = 0;
write_unlock_bh(&xfrm_policy_lock);
}
Cheers,
Kyle Moffett
BEGIN QUOTED CODE INVOLVING flow_cache_genid:
include/net/flow.h:94:
extern atomic_t flow_cache_genid;
as opposed
to uint32_t, which is also defined by libc, resulting in collisions
in naming.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP++
specific width.
That doesn't work for an ABI. If you switch compilers (or from 32-bit
to 64-bit like from x86 to x86-64, you _must_ be able to specify
certain widths for all the ABI numbers to preserve compatibility.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d
ng maintenance or porting their code,
they could start using those types.
The types _are_ available from the kernel headers, but only when
compiling with __KERNEL__, to avoid conflicts from the libc
definitions.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s+
But in a world with more than one register size, you _must_ use them,
for example, the x86-64 code uses them to handle 32-bit backwards
compatibility, and the ppc64 code does likewise. When a program
compiled as ppc32 gets run on my ppc64 box, the kernel understands
that anything pushed onto the s
On Apr 06, 2005, at 07:41, Renate Meijer wrote:
On Apr 6, 2005, at 12:11 AM, Kyle Moffett wrote:
Please don't remove Linux-Kernel from the CC, I think this is an
important discussion.
GAAH!!! Read my lips!!! Quit removing Linux-Kernel from the CC!!!
As I see it, there are a number of issues
blocks or large numbers of small objects (As you would
use a
slabcache for those), but it might help a bit. Of course, the code
would
need to fall back quickly if such an allocation would be messy or
expensive
for any reason.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
G
cannot be valid.
The only real point of most of the EULAs is to protect the owners
copyright, which is implicitly protected in any case.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E W++(+) N+++
omplet"..., 79) = 79
write(1, "# 3 Short offline Complet"..., 79) = 79
write(1, "# 4 Short offline Complet"..., 79) = 79
write(1, "# 5 Short offline Complet"..., 79) = 79
write(1, "# 6 Extended offlineComplet"..., 79) = 79
write(1,
.
Ok. Now if only I could find it. Is there anyplace in sysfs that I
can check manually to see what the dynamic major is? I'd like to
try creating the device by hand if I can't get Debian hotplug to see
it.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d-
e of the
following is probably true: you need to break the line up and use temps
for clarity, or your function is so big that you're tabbing over too
far.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
lyCaps all over :-D
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$ L(+
++) E
W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5
X R?
tv-(--) b(++) DI+ D+ G e->$ h!*()&g
former exhibits some similar (but not nearly as bad) symptoms. (Same
Powerbook), whereas 2.6.11 doesn't. In that case, neither has PREEMPT.
I'll run more tests this afternoon/evening, to try to track it down.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software de
hough I'm just getting back to testing things.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so
simple that there are obviously no deficiencies. And the other way is
to make
it so complicated that there are no obvious deficiencies. The
de of the patch. IIRC,
someone
was working on such a port, but it seems to have been lost along the way
at some point. Is there any additional information on that patch?
Cheers,
Kyle Moffett
--
Unix was not designed to stop people from doing stupid things,
because that
would also stop
On Aug 7, 2005, at 21:13:54, Kyle Moffett wrote:
On Aug 7, 2005, at 12:13:38, Benjamin Herrenschmidt wrote:
_However_ there is an unrelated problem with some panels,
including some
of the 17": The panel doesn't always "sync" properly. This seem to be
related to some subtle
new driver.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$ L(+
++) E
W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5
X R?
tv-(--) b(++) DI+ D+ G e->$ h!*()>++$ r !
ul to
allow
a simple new inheritance model for "capabilities", "roles",
"rootperms" or
whatever other abstraction you create.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so
simple that there are obviously no
n the PCI bus :-D,
and I'd be interested in an example of how that could work in any
sane way.
Cheers,
Kyle Moffett
--
Premature optimization is the root of all evil in programming
-- C.A.R. Hoare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bo
-kernel AFS client
could use it
in similar fashion (It has no method to adjust hierarchy, because
it's still
read-only). GFS could use it for their Context Dependent Symlinks.
Since it
would pass the type in as well, it would be possible to use it for
different
kinds of links on t
hings:
1) The least-significant bit is the first bit
2) The first bit is the _highest_ power of X.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$ L(+
++) E
W++(+) N+++(++) o? K? w--- O? M++ V?
be that, or it could be some kernel genius figured
out that one method is faster or better or more magical than
the other on most platforms. Since the code works well, I
would be disinclined to tinker with it. :-D.
Cheers,
Kyle Moffett
--
Q: Why do programmers confuse Halloween and Christmas?
A:
hough by that point you could write it backwards in a blindfold,
that has
_got_ to be hard and frustrating work.
Cheers,
Kyle Moffett
--
Somone asked me why I work on this free (http://www.fsf.org/philosophy/)
software stuff and not get a real job. Charles Shultz had the best
answer:
&q
wide variety of keysyms,
preferably all of UTF-8, and send them to the topmost window.
Cheers,
Kyle Moffett
--
Unix was not designed to stop people from doing stupid things,
because that
would also stop them from doing clever things.
-- Doug Gwyn
-
To unsubscribe from this list: send th
t when skipping ticks (IE: You probably don't need to do anything
special to replay missed ticks, the new timer code automatically
handles it
for you). There is an excellent LWN article on his project here:
http://lwn.net/Articles/120850/
Cheers,
Kyle Moffett
--
Simple things should b
!.?|" an operator??? Or "?^", "+|", "~|",
"?|", etc. I
think Larry's gone off the deep end on this one. It may be an
incredibly powerful
and expressive language, but it seems _really_ strange, and probably
will produce
the best Obfuscated-code contest t
does not block sig
sa_mask blocks sig
Cheers,
Kyle Moffett
--
Q: Why do programmers confuse Halloween and Christmas?
A: Because OCT 31 == DEC 25.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
do this:
cat firmware-with-checksum.img >/sys/devices/platform/dellbios/
firmware_upgrade
Then an ordinary system reboot or shutdown would automatically use
the SMI and
host-control-action to upgrade the firmware and shutdown or reboot,
instead of
the normal ACPI shutdown and reboot c
IMHO,
you've still got a ways to go. Keep up the good work, though!
Cheers,
Kyle Moffett
--
Unix was not designed to stop people from doing stupid things,
because that
would also stop them from doing clever things.
-- Doug Gwyn
-
To unsubscribe from this list: send the line "
On Aug 15, 2005, at 19:38:49, Doug Warzecha wrote:
On Mon, Aug 15, 2005 at 04:23:37PM -0400, Kyle Moffett wrote:
Why can't you just implement the system management actions in the
kernel
driver?
We want to minimize the amount of code in the kernel and avoid
having to
update the d
On Aug 16, 2005, at 00:34:51, Chris Wedgwood wrote:
On Mon, Aug 15, 2005 at 04:23:37PM -0400, Kyle Moffett wrote:
Why can't you just implement the system management actions in the
kernel driver?
Why put things in the kernel unless it's really needed?
I'm not thrillied ab
access rules
which kernel developers need to understand. I believe some simple
Googling and
grepping through the kernel code should reveal the necessary ptrace-
related
process checks.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so
bug a day or so ago when updating to
2.6.13-rc6,
it's just I noticed the error, fixed my config, then recompiled and
forgot
about it completely until now :-D. Thanks for the bug report, though!
Cheers,
Kyle Moffett
--
I have yet to see any problem, however complicated, which, when y
ull access
to the device node itself.
Cheers,
Kyle Moffett
--
Simple things should be simple and complex things should be possible
-- Alan Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More maj
cally to access the same file, and I
want to prevent one of my admins from accidentally editing that file
by hand. The best way is with a big comment in the file itself and
the immutable bit.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>
ctor-capable CPU (Like PPC), you
might find that people will buy them for the flexibility. Such a thing
might also be useful for the prezero folks, it could be used (when not
otherwise occupied) for zeroing unused pages.
Personally, I think I'd buy one or two just to tinker with them :-D.
On Jul 31, 2005, at 18:32:47, Pavel Machek wrote:
and cpufreq is usefull to keep your desktop cold, too.
But I don't want my desktop cold!!! That would ruin its usefulness as a
400W dorm space-heater!!! :-D
*starts boinc client running in the background*
Cheers,
Kyle Moffett
--
ms in -mm already).
Personally, I am of the opinion that if GFS cannot use jdb, the
developers
ought to clarify why it isn't useable, and possibly submit fixes to make
it useful, so that others can share the benefits.
Cheers,
Kyle Moffett
--
I lost interest in "blade servers"
xists, it would be called in both the
suspend and shutdown paths, before the suspend() and shutdown() calls to
that driver are made. As drivers are fixed to clean up and combine that
code, they could put the merged result into the powerdown() function,
and remove their suspend() and shutdown()
a single
"typedef unsigned short kmem_bufctl_t" in include/linux/types.h
Cheers,
Kyle Moffett
--
Premature optimization is the root of all evil in programming
-- C.A.R. Hoare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
On Aug 28, 2005, at 19:37:16, Adrian Bunk wrote:
On Sun, Aug 28, 2005 at 02:55:03PM -0700, Andrew Morton wrote:
Kyle Moffett <[EMAIL PROTECTED]> wrote:
While exploring the asm-*/types.h files, I discovered that the
type "kmem_bufctl_t" is differently defined across each plat
ted a complete lack of RTFM and STFW. Please
go read the associated documentation before asking questions, and then
ask them on the appropriate forum (if you still have questions).
Here is a good document about asking good questions:
http://www.catb.org/~esr/faqs/smart-questions.html
Cheers,
Kyle Mo
1 is unmounted, you
will get
an IN_UNMOUNT on the watch.
I think this might work as well:
# mount /dev/hda1 /mnt
# ./inotify_test /mnt/. &
# umount /mnt
That should get the effect you are looking for
Cheers,
Kyle Moffett
--
I have yet to see any problem, however complicated, which, when yo
s.
The script:
http://zeus.moffetthome.net/~kyle/hexfreq
The output:
http://zeus.moffetthome.net/~kyle/dwl.hexmult
Reprocessed output by frequency:
http://zeus.moffetthome.net/~kyle/dwl.hexfreq
Reprocessing command:
dwl.hexfreq
Cheers,
Kyle Moffett
--
Somone asked me why I work on this free (http://ww
practice it's easier to advance CLOCK_MONOTONIC/CLOCK_REALTIME
equally and only apply time jumps to CLOCK_REALTIME.
I thought that's what he said, but maybe I'm just confused :-D.
Cheers,
Kyle Moffett
--
Premature optimization is the root of all evil in programming
-- C.A.R. H
ly meant
linux/foo.h (See the types.h example), only to have it magically
work because some other header already included linux/types.h
anyways. If arch/driver/etc maintainers are willing to take patches
to clean that up, I'll start with that and eventually get a decent
set of kabi/* heade
On Sep 2, 2005, at 09:41:09, Erik Andersen wrote:
On Thu Sep 01, 2005 at 11:00:16PM -0400, Kyle Moffett wrote:
A while ago there was a big discussion about splitting out the
userspace-accessible portions of the kernel headers into a separate
directory, "kabi", "kernel-abi"
ear that others are
interested in the project, because maybe I won't need to do it _all_
myself :-D. I'll take a look at the patches mentioned, to get more
of an idea on the various technical issues.
Cheers,
Kyle Moffett
--
Simple things should be simple and complex things shou
On Sep 2, 2005, at 19:24:22, H. Peter Anvin wrote:
Kyle Moffett wrote:
My far-into-the-future ideal for this is to have a generic vDSO-type
library that is compiled into the kernel that provides a
collection of
architecture-optimized routines available in both kernelspace and
userspace by
bc/klibc/etc authors would
have the option of just doing "typedef _kabi_u32 uint32_t;" in their
header files.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$ L(+
++) E
W++(+) N+++(++) o? K
On Sep 2, 2005, at 20:34:11, H. Peter Anvin wrote:
Kyle Moffett wrote:
I would actually be more inclined to provide and use types like
_kabi_{s,u}{8,16,32,64}, etc. Then the glibc/klibc/etc authors would
have the option of just doing "typedef _kabi_u32 uint32_t;" in their
header fil
kcore/* and kabi/* that
define the appropriate types, then both userspace and the kernel
could use whatever types fit their fancy, defined in terms of the
__kcore_ and __kabi_ types, which could be _depended_ on to exist
because they are guaranteed not to conflict with other namespaces
Cheers,
Kyle
On Sep 3, 2005, at 01:57:26, H. Peter Anvin wrote:
Kyle Moffett wrote:
The world would be so much nicer a place if user space were free
to #include linux/* header files rather than keeping a
per-project private copy of all kernel structs of interest.
Exactly! This is why I want to create
t many apps
in userspace would cease to compile on standards compliant platforms.
Cheers,
Kyle Moffett
--
Somone asked me why I work on this free (http://www.fsf.org/philosophy/)
software stuff and not get a real job. Charles Shultz had the best
answer:
"Why do musicians compose symphonies and poe
_ino __stat64.st_ino
[...]
Then the userspace program could do this:
struct stat foo;
foo.st_ino = 0;
And it would be preprocessed into:
struct stat foo;foo.__stat64.st_ino = 0;
Cheers,
Kyle Moffett
--
Somone asked me why I work on this free (http://www.fsf.org/philosophy/)
software stuff and no
llocate
a separate ndiswrapper stack (IE: Not the kernel stacks). The kernel is
under no obligation not to break out-of-tree drivers, etc, even semi-
non-
-binary-only ones such as ndiswrapper. Figure out how to fix it and
move on!
Cheers,
Kyle Moffett
--
Q: Why do programmers confuse Hallo
ere to resolve the excessive
stack
usage and a few to do some sort of bio chaining (Instead of recursive
calls).
I don't remember what underlying hardware was behind the SCSI, but I
suspect
something like iSCSI or USB would push some extra stack in there for
stress
testing.
Cheers,
On Sep 5, 2005, at 12:35:42, H. Peter Anvin wrote:
Followup to: <[EMAIL PROTECTED]>
By author: Kyle Moffett <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
Didn't you mean "#define stat __kabi_stat64"? Also, I can see that
would pose other issues as well s
On Sep 5, 2005, at 19:28:07, Kyle Moffett wrote:
With all of that mess out of the way, I'll work on getting a few
initial RFC
patches out the door, and then we can revisit this discussion once
there is
something tangible to talk about.
Ugh. Step one for my cleanup is to r
yption entirely.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$ L(+
++) E
W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5
X R?
tv-(--) b(++) DI+ D+ G e->$ h!*()>++$
;t
determined what makes kswapd spin forever after it receives the
signal.
Probably a while(1) loop that isn't intended to stop until the machine
physically powers off. If you want to patch one specific kernel thread,
you might be able to do that, but you can't just expect to hot-pa
non-critical
failure; you might fail to fully sync a FUSE filesystem because its
daemon is asleep waiting on something (possibly even just sitting in
a "sleep(1)" call with all signals masked). You simply need to
make sure that all tasks are asleep outside of driver critical
unt count" numbers set to primes between 7 and 37
(depending on the filesystem) so that troubled or frequently-rebooted
systems are more frequently verified. The end result is that I
almost never have the dreaded 4-hour-fsck-on-boot problem. A drive
has certainly been fscked within the
s this a good way to use sched_yield()? Maybe, maybe not. But it
*is* an actual use of the API in a real app.
We weren't looking for "actual uses", especially not in binary-only
apps. What we are looking for is optimal uses of sched_yield(); ones
where that is the best alternativ
redundant.
For maximum readability and cleanliness I recommend that you leave off
the "extern" on the function declarations; it makes the lines much
longer without obvious gain.
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-ker
in SELinux, and
efforts would be better spent in figuring out what seems too
complicated in SELinux and making it simpler. Probably a fair amount
of that just means better tools.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Oct 05, 2007, at 00:45:17, Eric W. Biederman wrote:
Kyle Moffett <[EMAIL PROTECTED]> writes:
On Oct 04, 2007, at 21:44:02, Eric W. Biederman wrote:
SElinux is not all encompassing or it is generally
incomprehensible I don't know which. Or someone long ago would
have said a
becomes a noticeably
invalid __attribute__((__attribute__((__pure__
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ent bug) from what we've done
for a while. You might want to do a git-blame on this bit of code to
see who the last person to modify it was and ask them to test or
confirm the patch first. The same general questions apply to the
other logical-op bugs.
Cheers,
Kyle Moffett
-
To unsub
pen for up to a
year or so.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
m still not seeing anything
which SELinux cannot directly implement without additional code, even
the "CAP_MAC_OVERRIDE" bit. If the semantics don't seem quite right,
please provide details about how you think the models differ and I
will try to address the concerns.
Ch
On Oct 11, 2007, at 11:41:34, Casey Schaufler wrote:
--- Kyle Moffett <[EMAIL PROTECTED]> wrote:
[snipped]
I'm still waiting to see the proposed SELinux policy that does what
Smack does.
That *is* the SELinux policy which does what Smack does. I keep
having bugs in the perl
run an optimistically-real-time
game as one user and several thousand busy-loops as another user and
get almost picture perfect 50% CPU distribution between the users.
To me that seems a much better DoS-prevention system than limits
which don't scale based on how many people are request
On Oct 12, 2007, at 01:37:23, Al Boldi wrote:
Kyle Moffett wrote:
This isn't really necessary any more with the new CFS scheduler.
If you want to prevent excess memory usage then you limit memory
usage, not process count, so just set the system max process count
to something absurdly
ng debugged, but under Linux it's effectively impossible
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ed to use the appropriate commands, same as every
other VCS on the planet.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Nov 30, 2007, at 13:40:07, H. Peter Anvin wrote:
Kyle Moffett wrote:
With that said, there is a significant performance penalty as all
Objective-C method calls are looked up symbolically at runtime for
every single call.
GACK!
At least C++ has vtables.
In a tight loop there is a way
n the kernel though, there are many
codepaths where *every* *single* instruction counts; that could be a
serious performance hit.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majord
using it in whatever fashion they desire. Typically if you price
your software reasonably people will be willing to pay for multiple
copies but there are no foolproof technical measures to enforce that
they do so.
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsub
er lock (except during crash, where we break locks
already for printk()), and I doubt any of the callers would notice
the serialization since they're already serialized on the printk buffer.
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
nd use-cases for
why it cannot be implemented in user-space or with small
modifications to existing UDP/TCP networking.
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
etwork would be expensive, but I believe the cost would
be reasonable for many applications and it would allow traditional
atomic ops on the mapped pages to take and release futexes in the
uncontended case.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux
r embedded architectures have very similar problems. Some may
provide an "unaligned data access" exception, but offer insufficient
information to repair the damage and resume execution.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
en the ability to take any action on any object by
rules in the policy, and it typically still falls under a few MLS
labeling restrictions even in the targeted policy.
Cheers,
Kyle Moffett
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
On Nov 24, 2007, at 22:36:43, Crispin Cowan wrote:
Kyle Moffett wrote:
Actually, a fully-secured strict-mode SELinux system will have no
unconfined_t processes; none of my test systems have any.
Generally "unconfined_t" is used for situations similar to what
AppArmor was de
k first, although that
could be fixed with a few VFS and blockdev hooks which hierarchically
flush and "freeze" block devices and filesystems before actually
disabling devices much the way that device-mapper can pause a device
to take a snapshot and end up with a clean journal
handler which
hooks into Xen code very precisely to create and preserve the "No
pending page table updates" state that you care about. It will be
more work in the short term but it's the only maintainable solution
in the long term IMO.
Cheers,
Kyle Moffett
-
To unsubscribe from
er to it (and
possibly respond in kind with documentation patches).
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
g them out involves calling a
userspace
process which may allocate RAM, etc.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(++
In include/asm-sparc/types.h, __kernel_nlink_t is signed, whereas on
all the
other architectures it is unsigned. Is this intentional, or a bug?
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E
ll over the place on kernel upgrade, we're ok.
I don't mind adding new options for advanced security, as long
as you don't change the defaults. It's hard enough managing
a boatload of workstations under ideal conditions. When the
default settings change every month it gets re
the nr_cpus readers
preempted on one CPU. It gets pretty messy
One solution I can think of, although it bloats memory usage for
many-way
boxen, is to just have a table in the rwlock with one entry per cpu.
Each
CPU would get one concurrent reader, others would need to sleep
Cheers,
Kyle Moffett
notify on /dev (For the udev case) should allow it to
detect when the device is available.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
user-limits
in the kernel, the existing one works fine for most purposes, when
combined with appropriate administrative tools.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E W++(+) N+++(++) o? K?
y such a system will need a _LOT_ of work and
testing to make sure it doesn't break existing setups. Oh well, I can
dream, can't I? :-D
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$ P+++()>$
L(+++) E
has been deprecated and mostly unmaintained since before
2.6.0 was released, so it really doesn't surprise me. Go download
and install udev, hotplug, etc from your distro.
Cheers,
Kyle Moffett
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCM/CS/IT/U d- s++: a18 C>$ UB/L/X/*(+)>$
1 - 100 of 360 matches
Mail list logo
