, but the other case is more important.
Does a parent death signal make most sense between processes that are part of
a larger program.
That is the only way I can really see it being used. The only actual
example of use I know is what Albert Cahalan reported. To my mind, the
only semantics that matter
On 2/28/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
Starting with kernel 2.6.19, the process directories in
/proc are sorted by number. They were sorted by process
start time in 2.6.18 and earlier. This makes the output
of procps come out in that
On Nov 29, 2007 4:40 PM, Eric W. Biederman [EMAIL PROTECTED] wrote:
Albert Cahalan [EMAIL PROTECTED] writes:
On Nov 28, 2007 6:31 AM, Eric W. Biederman [EMAIL PROTECTED] wrote:
Ingo Molnar [EMAIL PROTECTED] writes:
* Albert Cahalan [EMAIL PROTECTED] wrote:
On Nov 27, 2007 7:49 PM
, unlike with the
proposed interface change.
Ccing Albert Cahalan as he made the change to /proc/self in the first
place:
Changing /proc/self is somewhat risky, and probably
undesirable anyway. That file has always been used
to represent the process; at one time this also meant
the task
On Nov 28, 2007 6:31 AM, Eric W. Biederman [EMAIL PROTECTED] wrote:
Ingo Molnar [EMAIL PROTECTED] writes:
* Albert Cahalan [EMAIL PROTECTED] wrote:
On Nov 27, 2007 7:49 PM, Guillaume Chazarain [EMAIL PROTECTED] wrote:
In a lot of ways if you access /proc/self and you get back information
On Nov 28, 2007 5:46 AM, Ingo Molnar [EMAIL PROTECTED] wrote:
* Albert Cahalan [EMAIL PROTECTED] wrote:
On Nov 27, 2007 7:49 PM, Guillaume Chazarain [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
We may be stuck with the current broken behavior for backwards
compatibility
Linus Torvalds writes:
NOTE! I detest the centralized SCM model, but if push comes to shove,
and we just _can't_ get a reasonable parallell merge thing going in
the short timeframe (ie month or two), I'll use something like SVN
on a trusted site with just a few committers, and at least try to
On Sun, 2005-04-10 at 17:38 +0200, Rene Scharfe wrote:
Albert, allowing access based on tty sounds nice, but it _is_ expansive.
More importantly, perhaps, it would virtualize /proc: every user would
see different permissions for certain files in there. That's too comlex
for my taste.
If you
OK, folks, another try to enhance privacy by hiding
process details from other users. Why not simply use
chmod to set the permissions of /proc/pid directories?
This patch implements it.
Children processes inherit their parents' proc
permissions on fork. You can only set (and remove)
read
On Mon, 2005-03-14 at 10:42 +0100, Rene Scharfe wrote:
Albert Cahalan wrote:
This is a bad idea. Users should not be allowed to
make this decision. This is rightly a decision for
the admin to make.
Why do you think users should not be allowed to chmod their processes'
/proc directories
On Mon, 2005-03-14 at 12:27 -0800, Matt Mackall wrote:
On Mon, Mar 14, 2005 at 12:04:07PM -0800, john stultz wrote:
+static inline cycle_t read_timesource(struct timesource_t* ts)
+{
+ switch (ts-type) {
+ case TIMESOURCE_MMIO_32:
+
On Tue, 2005-03-15 at 00:08 +0100, Bodo Eggert wrote:
On Mon, 14 Mar 2005, Albert Cahalan wrote:
On Mon, 2005-03-14 at 10:42 +0100, Rene Scharfe wrote:
Albert Cahalan wrote:
Why do you think users should not be allowed to chmod their processes'
/proc directories? Isn't it similar
On Mon, 2005-03-14 at 19:22 -0800, Christoph Lameter wrote:
On Mon, 14 Mar 2005, Albert Cahalan wrote:
When the vsyscall page is created, copy the one needed function
into it. The kernel is already self-modifying in many places; this
is nothing new.
AFAIK this will only works on ia32
On Tue, 2005-03-15 at 15:31 +0100, Bodo Eggert wrote:
(snipped the CC list - hope that's ok)
On Mon, 14 Mar 2005, Albert Cahalan wrote:
On Tue, 2005-03-15 at 00:08 +0100, Bodo Eggert wrote:
On Mon, 14 Mar 2005, Albert Cahalan wrote:
This really isn't about security.
Information
Russell King, the latest person to notice defects, writes:
However, the way the kernel is setup today, this seems
impossible to achieve, which tends to make the whole
idea of capabilities completely and utterly useless.
How is this stuff supposed to work? Are my ideas of
what's supposed to
On Wed, 2005-03-16 at 03:39 +0100, Rene Scharfe wrote:
So, I gather from the feedback I've got that chmod'able /proc/pid
would be a bit over the top. 8-) While providing the easiest and most
intuitive user interface for changing the permissions on those
directories, it is overkill. Paul is
Better interface:
/sbin/sysctl -w proc.maps=0440
/sbin/sysctl -w proc.cmdline=0444
/sbin/sysctl -w proc.status=0444
The /etc/sysctl.conf file can be used to set these
at boot time.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Thu, 2005-03-17 at 16:55 +, Russell King wrote:
On Tue, Mar 15, 2005 at 10:23:54AM -0500, Albert Cahalan wrote:
On Mon, 2005-03-14 at 19:22 -0800, Christoph Lameter wrote:
On Mon, 14 Mar 2005, Albert Cahalan wrote:
When the vsyscall page is created, copy the one needed
On Sun, 2005-03-20 at 01:22 +0100, Rene Scharfe wrote:
The permissions of files in /proc/1 (usually belonging to init) are
kept as they are. The idea is to let system processes be freely
visible by anyone, just as before. Especially interesting in this
regard would be instances of login. I
Christoph Hellwig writes:
On Sat, Mar 05, 2005 at 07:40:06PM -0500, Robert Love wrote:
On Sun, 2005-03-06 at 00:04 +, Christoph Hellwig wrote:
The user interface is still bogus.
I presume you are talking about the ioctl. I have tried to engage you
and others on what exactly you prefer
Lennart Sorensen writes:
You forgot the very important:
- Only works on architecture it was compiled for. So anyone not
using i386 (and maybe later x86-64) is simply out of luck. What do
nvidia users that want accelerated nvidia drivers for X DRI do
right now if they have
Peter Chubb writes:
There are three new system calls:
long usr_pci_open(int bus, int slot, int function, __u64 dma_mask);
Returns a filedescriptor for the PCI device described
by bus,slot,function. It also enables the device, and sets it
up as a
On Fri, 2005-03-11 at 19:15 +, Alan Cox wrote:
You forgot the PCI domain (a.k.a. hose, phb...) number.
Also, you might encode bus,slot,function according to
the PCI spec. So that gives:
long usr_pci_open(unsigned pcidomain, unsigned devspec, __u64 dmamask);
Still insufficient
greg k-h writes:
On Sat, Mar 26, 2005 at 10:30:20PM -0500, Lee Revell wrote:
That's the problem, it's not spelled out explicitly anywhere.
That file does not address the issue of whether a driver is
a derived work. This is the part he should talk to a lawyer
about, right?
How about the
[quoting various people...]
Here is a new entry developed for /proc that prints for each process
memory area (VMA) the size of rss. The maps from original kernel is
able to present the virtual size for each vma, but not the physical
size (rss). This entry can provide an additional
Assuming you'd like ps to print the LUID, how about
putting it with all the others? There are Uid:
lines in the /proc/*/status files.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, 2005-02-24 at 22:49 -0800, Chris Wright wrote:
* Albert Cahalan ([EMAIL PROTECTED]) wrote:
Assuming you'd like ps to print the LUID, how about
putting it with all the others? There are Uid:
lines in the /proc/*/status files.
It's also set (written) via /proc, so it should
On 1/4/07, Segher Boessenkool [EMAIL PROTECTED] wrote:
Adjusting gcc flags to eliminate optimizations is another way to go.
Adding -fwrapv would be an excellent start. Lack of this flag breaks
most code which checks for integer wrap-around.
Lack of the flag does not break any valid C code,
I have a fun little test program for people to try. It creates zombies
that persist until reboot, despite being reparented to init. Sometimes
it creates processes that block SIGKILL, sit around with pending SIGKILL,
or both.
You'll want:
a. either assembly skills or the ability to run 32-bit
Somebody PLEASE try this...
Normally, when a process dies it becomes a zombie.
If the parent dies (before or after the child), the child
is adopted by init. Init will reap the child.
The program included below DOES NOT get reaped.
Do like so:
gcc -m32 -O2 -std=gnu99 -o foo foo.c
while true;
David Wragg writes:
Benjamin LaHaise [EMAIL PROTECTED] writes:
On Mon, Dec 18, 2006 at 11:50:08PM +, David Wragg wrote:
This patch (against 2.6.19/2.6.19.1) adds the four context
switch values (voluntary context switches, involuntary
context switches, and the same values accumulated from
On 12/20/06, Mike Galbraith [EMAIL PROTECTED] wrote:
On Tue, 2006-12-19 at 21:46 -0500, Albert Cahalan wrote:
Somebody PLEASE try this...
I was having enough fun with cloninator (which was whitespace munged
btw).
Anything stuck? Besides refusing to die, that beast slays debuggers
left
Karel Zak writes:
I've originally thought about util-linux upstream fork,
but as usually an fork is bad step. So.. I'd like to start
some discussion before this step.
...
after few weeks I'm pleased to announce a new util-linux-ng
project. This project is a fork of the original util-linux
On 12/20/06, Jan Engelhardt [EMAIL PROTECTED] wrote:
I've originally thought about util-linux upstream fork,
but as usually an fork is bad step. So.. I'd like to start
some discussion before this step.
...
after few weeks I'm pleased to announce a new util-linux-ng
project. This project
On 12/20/06, David Wragg [EMAIL PROTECTED] wrote:
Albert Cahalan [EMAIL PROTECTED] writes:
On Mon, Dec 18, 2006 at 11:50:08PM +, David Wragg wrote:
This patch (against 2.6.19/2.6.19.1) adds the four context
switch values (voluntary context switches, involuntary
context switches
Linus Torvalds writes:
So it would appear that for OS X, the
#define _XOPEN_SOURCE_EXTENDED 1 /* AIX 5.3L needs this */
#define _GNU_SOURCE
#define _BSD_SOURCE
sequence actually _disables_ those things.
Yes, of course. The odd one here is glibc.
Normal systems enable
There are big nasty bugs related to threaded processes exiting,
especially when involving: zombie leaders, clone w/o SIGCHLD,
and ptrace. I can make tasks that remain until reboot. I've seen
things stuck in X state. I've seen pending SIGKILL and even
blocked SIGKILL. I've seen D state pretending
David Singleton writes:
Add variation of /proc/PID/smaps called /proc/PID/pagemaps.
Shows reference counts for individual pages instead of aggregate totals.
Allows more detailed memory usage information for memory analysis tools.
An example of the output shows the shared text VMA for ld.so and
I had one share mounted, from XP to Linux, and wanted another.
At first I had an incorrect setting on the XP box, almost
certainly related to permissions. The mount failed of course.
Running mount showed that the filesystem was not mounted,
but apparently it didn't remain fully unmounted either.
On 7/7/07, Satyam Sharma [EMAIL PROTECTED] wrote:
On 7/7/07, Albert Cahalan [EMAIL PROTECTED] wrote:
I had one share mounted, from XP to Linux, and wanted another.
At first I had an incorrect setting on the XP box, almost
certainly related to permissions. The mount failed of course.
Running
On 6/7/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
So it looks to me like we need to do three things:
- Fix the inode number
- Fix the name on the hugetlbfs dentry to hold the key
- Add a big fat comment that user space programs depend on this
behavior of both the dentry name and the inode
Right now, Linux isn't all that friendly to JIT emulators.
Here are the problems and suggestions to improve the situation.
There is an SE Linux execmem restriction that enforces W^X.
Assuming you don't wish to just disable SE Linux, there are
two ugly ways around the problem. You can mmap a file
On 6/8/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Albert Cahalan [EMAIL PROTECTED] writes:
On 6/7/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
So it looks to me like we need to do three things:
- Fix the inode number
- Fix the name on the hugetlbfs dentry to hold the key
- Add
On 6/8/07, Eric Dumazet [EMAIL PROTECTED] wrote:
Albert Cahalan a écrit :
Additions to better support JIT emulators:
a. sysctl to set IPC_RMID by default
Not very good, this will break some apps.
As a sysctl, the admin gets to choose between
compatibility and sanity.
I can see
On 6/8/07, Alan Cox [EMAIL PROTECTED] wrote:
There is an SE Linux execmem restriction that enforces W^X.
This depends on whatever SELinux rulesets you are running. Its just a
good rule to have present that most programs shouldn't be self patching,
and then label those that do differently.
A
Neat! It's great to see somebody else waking up to the idea that
storage media is NOT to be trusted.
Judging by the design paper, it looks like your structs have some
alignment problems.
The usual wishlist:
* inode-to-pathnames mapping
* a subvolume that is a single file (disk image, database,
On 6/13/07, Chris Mason [EMAIL PROTECTED] wrote:
On Wed, Jun 13, 2007 at 01:45:28AM -0400, Albert Cahalan wrote:
The usual wishlist:
* inode-to-pathnames mapping
This one I'll code, it will help with inode link count verification. I
want to be able to detect at run time that an inode
On 6/13/07, Chris Mason [EMAIL PROTECTED] wrote:
On Wed, Jun 13, 2007 at 12:14:40PM -0400, Albert Cahalan wrote:
On 6/13/07, Chris Mason [EMAIL PROTECTED] wrote:
On Wed, Jun 13, 2007 at 01:45:28AM -0400, Albert Cahalan wrote:
* secure delete via destruction of per-file or per-block random
Christoph Hellwig writes:
On Thu, Jun 14, 2007 at 04:36:09PM +0900, Kentaro Takeda wrote:
We limit the maximum length of any string data (such as
domainname and pathnames) to TOMOYO_MAX_PATHNAME_LEN
(which is 4000) bytes to fit within a single page.
Userland programs can obtain the amount of
On 6/15/07, Pavel Machek [EMAIL PROTECTED] wrote:
[Albert Cahalan]
It's really not worth getting bothered by. Truth is, big
giant
pathnames break lots of stuff already, both kernel and
userspace.
Just look in /proc for some nice juicy kernel breakage:
cwd, exe, fd/*, maps, mounts
On 6/19/07, William Lee Irwin III [EMAIL PROTECTED] wrote:
On Fri, Jun 08, 2007 at 02:35:22AM -0400, Albert Cahalan wrote:
Right now, Linux isn't all that friendly to JIT emulators.
Here are the problems and suggestions to improve the situation.
There is an SE Linux execmem restriction
On 6/20/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
William Lee Irwin III wrote:
I presumed an ELF note or extended filesystem attributes were already
in place for this sort of affair. It may be that the model implemented
is so restrictive that users are forbidden to create new
.
On Tue, Jun 19, 2007 at 11:16:29PM -0400, Albert Cahalan wrote:
It does and it doesn't. There is not a reasonable way for a
user to mark an app as needing full self-modifying ability.
It's not like the executable stack, which can be set via the
ELF note markings on the executable. (ELF note markings
On 6/20/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Albert Cahalan wrote:
Putting this into the security policy was an error born of
lazyness to begin with. Abuse of the security mechanism
was easier than hacking the toolchain, ELF loader, etc.
Either a binary needs self-modification
On 6/20/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Albert Cahalan wrote:
Look, let's back up a bit here. At a high level, what exactly do
you imagine that this behavior was intended for? I suggest you
list some examples of the attacks that are blocked.
Can you come up with a reasonable
On 6/21/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
On Fri, 2007-06-08 at 02:35 -0400, Albert Cahalan wrote:
Right now, Linux isn't all that friendly to JIT emulators.
Here are the problems and suggestions to improve the situation.
There is an SE Linux execmem restriction that enforces W^X
On 6/21/07, Pavel Machek [EMAIL PROTECTED] wrote:
It's really not worth getting bothered by. Truth is, big
giant
pathnames break lots of stuff already, both kernel and
userspace.
Just look in /proc for some nice juicy kernel breakage:
cwd, exe, fd/*, maps, mounts, mountstats,
On 6/22/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
On Fri, 2007-06-22 at 01:56 -0400, Albert Cahalan wrote:
On 6/21/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
On Fri, 2007-06-08 at 02:35 -0400, Albert Cahalan wrote:
Right now, Linux isn't all that friendly to JIT emulators.
Here
On 6/22/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
and these methods also destroy yourself on any machine with a looser
cache coherency between I and D-cache
for all but x86 you pretty much have to do the mprotect() between the
two states to deal with the cache
Ingo Molnar writes:
looking over the list of our new generic APIs (see further below) i
think there are three important things that are needed for an API to
become widely used:
1) it should solve a real problem (ha ;-), it should be intuitive to
humans and it should fit into existing
David Schwartz writes:
[Aaron Wiebe]
open(/somefile, O_WRONLY|O_NONBLOCK|O_CREAT, 0644) = 1621 0.415147
How could they make any difference? I can't think of any
conceivable way they could.
Now, I'm a userspace guy so I can be pretty dense, but shouldn't a
call with a nonblocking flag
Eric W. Biederman writes:
Badari Pulavarty [EMAIL PROTECTED] writes:
Your recent cleanup to shm code, namely
[PATCH] shm: make sysv ipc shared memory use stacked files
took away one of the debugging feature for shm segments.
Originally, shmid were forced to be the inode numbers and
they
On 6/6/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Wed, 6 Jun 2007 23:27:01 -0400 Albert Cahalan [EMAIL PROTECTED] wrote:
Eric W. Biederman writes:
Badari Pulavarty [EMAIL PROTECTED] writes:
Your recent cleanup to shm code, namely
[PATCH] shm: make sysv ipc shared memory use stacked
On 6/7/07, Badari Pulavarty [EMAIL PROTECTED] wrote:
BTW, I agree with Eric that its would be nice to use shmid as part
of name instead of forcing to be as inode number. It should be
possible for pmap to workout shmid from key or name. Isn't it ?
It is not at all nice.
1. it's incompatible
Robin Holt writes:
On Mon, Apr 09, 2007 at 08:36:21AM -0600, Eric W. Biederman wrote:
Robin Holt [EMAIL PROTECTED] writes:
I would say this is more a benefit than a problem. With a couple
of these systems we are testing, the number of kernel threads is
far greater than the number of user
Jan Engelhardt writes:
On Apr 10 2007 17:47, Jan Engelhardt wrote:
On Apr 8 2007 20:57, Oleg Nesterov wrote:
Anyway, re-parenting to swapper breaks pstree, it doesn't
show kernel threads. And if -parent == /sbin/init, we can't
remove us from -children (unless we forbid sub-thread-of-init
On 5/29/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Albert Cahalan [EMAIL PROTECTED] writes:
Jan Engelhardt writes:
-if(self_pid==1 ADOPTED(processes[i]) forest_type!='u')
+if(ADOPTED(processes[i]) forest_type!='u')
That's not compatible because init's children are now
Olaf Hering writes:
On Sat, Jul 14, H. Peter Anvin wrote:
Olaf Hering wrote:
Declare PAGE_SIZE as getpagesize() for userspace.
PAGE_SIZE is used in resource.h and shm.h
I would think it would be better to not define it at all.
Several architectures already don't have PAGE_SIZE visible
to
On 7/14/07, David Miller [EMAIL PROTECTED] wrote:
From: Albert Cahalan [EMAIL PROTECTED]
Date: Sat, 14 Jul 2007 22:48:57 -0400
A real constant-value PAGE_SIZE is useful and doable.
It's bogus to use it. The kernel can get recompiled
to arbitrary page sizes on some architectures, so a constat
Andrey Borzenkov writes:
This was posted in one of Russian forums. It was not possible to
archive (under Linux, using tar) vfat directory where files had
long Russian names (really long - over 150 - 170 characters) - tar
returned stat failure. When looking with plain ls, file names
appeared
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], linux-kernel@vger.kernel.org,
[EMAIL PROTECTED], [EMAIL PROTECTED]
Re: [PATCH 0/2] LogFS take two
You seem to be missing the immutable bit. This is really useful
for dealing with buggy or badly-designed things running as root.
I've used
On 5/8/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
On May 8 2007 00:43, Albert Cahalan wrote:
Fix: the vfat driver should use the 8.3 name for such files.
Or the 31-character ISO Level 1(?).
That might be appropriate for a similar problem on CD-ROM
filesystems. (when the CD is rockridge
On 5/9/07, Andrey Borzenkov [EMAIL PROTECTED] wrote:
On Wednesday 09 May 2007, Albert Cahalan wrote:
...
On May 8 2007 00:43, Albert Cahalan wrote:
Fix: the vfat driver should use the 8.3 name for such files.
...
It's not appropriate for vfat, HPFS, JFS, or NTFS. All of those
have built
Please don't forget the immutable bit. (man lsattr)
Having both, BSD-style, would be even better.
The immutable bit is important for working around
software bugs and features that damage files.
I also can't find xattr support.
-
To unsubscribe from this list: send the line unsubscribe
Sergei Shtylyov writes:
Kumar Gala wrote:
[Sergei Shtylyov]
Kumar Gala wrote:
I haven't looked at all the new clock/timer code, is there any
utility in having support for more than one clock source?
Of course, you may register as many as you like.
Sure, but is there any utility in
On 5/18/07, Sergei Shtylyov [EMAIL PROTECTED] wrote:
Albert Cahalan wrote:
Sure, but is there any utility in registering more than the
decrementer on PPC?
Not yet. I'm not sure I know any other PPC CPU facility fitting
for clockevents. In theory, FIT could be used -- but its period
On 5/19/07, Segher Boessenkool [EMAIL PROTECTED] wrote:
[Albert Cahalan]
Set MMCR0[TBEE], set MMCR0[PMXE], and choose a TBL bit via
MMCR0[TBSEL].
That's the performance monitor, which could very well be
in use already (for performance monitoring stuff, who
would have guessed
Why can we still not do this?
It's a stupid restriction. Security isn't a reason;
we have SE Linux policy and auditing to take
care of any issues. Heck, SE Linux policy could
even deny this feature for the truly paranoid.
Writing to /dev/* to update timestamps is surely
a worse security
I'm having problems with a font I just created. It's a rather big one,
intended for a framebuffer console in UTF-8 mode. The strace program
reports that /bin/setfont fails on a KDFONTOP ioctl with EINVAL.
In reading the kernel code, I find this:
vt.c:static int con_font_set(struct vc_data *vc,
On 5/1/07, H. Peter Anvin [EMAIL PROTECTED] wrote:
Antonino A. Daplas wrote:
And this will entail a lot of work to change (Is it worth it to rework
the code and remove the limitation?). The linux-console project
(http://linuxconsole.sourceforge.net/) might have , but I don't know its
On 5/2/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
On May 1 2007 11:49, Albert Cahalan wrote:
Well, I think the consensus is that anything beyond that should be done
in userspace; the main such console daemon was Kon2 last I checked.
Font size is not a sane place to draw the line. Features
On 5/3/07, Jan Engelhardt [EMAIL PROTECTED] wrote:
On May 3 2007 02:17, Albert Cahalan wrote:
Those sizes are unreadable on the 200 dpi OLPC XO screen,
Hm that should have read, for you:
I don't object implementing support for larger sizes.
(But I wonder how that should work without FB
Andrew Morton writes:
Cabot, Mason B [EMAIL PROTECTED] wrote:
I've been testing the NAS performance of ext3/Openfiler 2.2 against
NTFS/WinXP and have found that NTFS significantly outperforms ext3 for
video workloads. The Windows CIFS client will attempt a poor-man's
pre-allocation of the
john stultz writes:
Indeed. The monotonic clock's behavior around suspend and resume
is poorly defined. When we increased it, folks didn't like the
fact that uptime would increase while a system was suspended.
The uptime really does need to increase during suspend. Otherwise,
things get
This bug was introduced with SE Linux, 18 years ago. People have been
adding hacks to work around it as the bug bites them, but really the
bug ought to be fixed. Signals related to a tty are supposed to come
from the kernel. This got broken for pty devices. We now act as if
the signal is sent from
We got into the current situation for performance reasons, avoiding the costly
reload of CR3 that a hardware task switch would cause. It seems we'll be
loading CR3 now anyway, so it might be time to reconsider hardware
task switches.
The recent patches leave kernel entry/exit code mapped.
greg k-h writes:
> On Sat, Mar 26, 2005 at 10:30:20PM -0500, Lee Revell wrote:
>> That's the problem, it's not spelled out explicitly anywhere.
>> That file does not address the issue of whether a driver is
>> a "derived work". This is the part he should talk to a lawyer
>> about, right?
>
> How
Linus Torvalds writes:
> NOTE! I detest the centralized SCM model, but if push comes to shove,
> and we just _can't_ get a reasonable parallell merge thing going in
> the short timeframe (ie month or two), I'll use something like SVN
> on a trusted site with just a few committers, and at least
On Sun, 2005-04-10 at 17:38 +0200, Rene Scharfe wrote:
> Albert, allowing access based on tty sounds nice, but it _is_ expansive.
> More importantly, perhaps, it would "virtualize" /proc: every user would
> see different permissions for certain files in there. That's too comlex
> for my taste.
Christoph Hellwig writes:
> On Sat, Mar 05, 2005 at 07:40:06PM -0500, Robert Love wrote:
>> On Sun, 2005-03-06 at 00:04 +, Christoph Hellwig wrote:
>>> The user interface is still bogus.
>>
>> I presume you are talking about the ioctl. I have tried to engage you
>> and others on what
Lennart Sorensen writes:
> You forgot the very important:
>- Only works on architecture it was compiled for. So anyone not
> using i386 (and maybe later x86-64) is simply out of luck. What do
> nvidia users that want accelerated nvidia drivers for X DRI do
> right now if they
Peter Chubb writes:
> There are three new system calls:
>
> long usr_pci_open(int bus, int slot, int function, __u64 dma_mask);
> Returns a filedescriptor for the PCI device described
> by bus,slot,function. It also enables the device, and sets it
> up as a
On Fri, 2005-03-11 at 19:15 +, Alan Cox wrote:
> > You forgot the PCI domain (a.k.a. hose, phb...) number.
> > Also, you might encode bus,slot,function according to
> > the PCI spec. So that gives:
> >
> > long usr_pci_open(unsigned pcidomain, unsigned devspec, __u64 dmamask);
>
> Still
> OK, folks, another try to enhance privacy by hiding
> process details from other users. Why not simply use
> chmod to set the permissions of /proc/ directories?
> This patch implements it.
>
> Children processes inherit their parents' proc
> permissions on fork. You can only set (and remove)
>
On Mon, 2005-03-14 at 10:42 +0100, Rene Scharfe wrote:
> Albert Cahalan wrote:
> > This is a bad idea. Users should not be allowed to
> > make this decision. This is rightly a decision for
> > the admin to make.
>
> Why do you think users should not be allowed to chmo
On Mon, 2005-03-14 at 12:27 -0800, Matt Mackall wrote:
> On Mon, Mar 14, 2005 at 12:04:07PM -0800, john stultz wrote:
> > > > > > > > +static inline cycle_t read_timesource(struct timesource_t* ts)
> > > > > > > > +{
> > > > > > > > + switch (ts->type) {
> > > > > > > > + case
On Tue, 2005-03-15 at 00:08 +0100, Bodo Eggert wrote:
> On Mon, 14 Mar 2005, Albert Cahalan wrote:
> > On Mon, 2005-03-14 at 10:42 +0100, Rene Scharfe wrote:
> > > Albert Cahalan wrote:
>
> > > Why do you think users should not be allowed to chmod their processes'
&
[quoting various people...]
> Here is a new entry developed for /proc that prints for each process
> memory area (VMA) the size of rss. The maps from original kernel is
> able to present the virtual size for each vma, but not the physical
> size (rss). This entry can provide an additional
Assuming you'd like ps to print the LUID, how about
putting it with all the others? There are "Uid:"
lines in the /proc/*/status files.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, 2005-02-24 at 22:49 -0800, Chris Wright wrote:
> * Albert Cahalan ([EMAIL PROTECTED]) wrote:
> > Assuming you'd like ps to print the LUID, how about
> > putting it with all the others? There are "Uid:"
> > lines in the /proc/*/status files.
>
>
1 - 100 of 173 matches
Mail list logo
