On Sun, 2007-04-08 at 23:09 -0700, Andrew Morton wrote:
> On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
>
> > When I was examining the following program ...
> >
> > 1. There are a large amount of small jobs takes several msecs,
> > and the number of job incr
On Sun, 2007-04-08 at 21:34 +0300, Al Boldi wrote:
> Mike Galbraith wrote:
> > On Sat, 2007-04-07 at 19:17 +0200, Mike Galbraith wrote:
> > > I lowered the time to 500us, and ran at nice -10.. it starves tenpercent
> > > here every time. (ran as taskset -c 1 nice -n -10 ./fairtest) The
> > > star
On Mon, 2007-04-09 at 01:23 -0400, Gene Heskett wrote:
> This may not be so informative, its almost behaving ATM.
>
> 29252 amanda22 0 1856 572 220 R 76.4 0.1 1:07.24 gzip
> 29235 amanda15 0 2992 1224 888 S 5.6 0.1 0:02.80 chunker
> 29500 root 18 0 2996 1164 788 S
On Sat, 07 Apr 2007 16:31:39 +0900 Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
> When I was examining the following program ...
>
> 1. There are a large amount of small jobs takes several msecs,
> and the number of job increases constantly.
> 2. The process creates a thread or a process p
On Mon, 2007-04-09 at 01:16 -0400, Gene Heskett wrote:
> On Monday 09 April 2007, Mike Galbraith wrote:
> >So tar -cvf - / | gzip --best | tar -tvzf - should reproduce the
> >problem?
> >
> > -Mike
>
> That looks as if it should demo it pretty well if I understand correctly
> everything you'r
On Mon, 2007-04-09 at 00:08 -0400, Gene Heskett wrote:
> On Monday 09 April 2007, Mike Galbraith wrote:
> >
> >
> >Actually, there was practically nil interest in testing. We made a
> >couple of minor adjustments to the interactivity logic, and all went
> >quiet, so I didn't think it was enough of
On Mon, 2007-04-09 at 02:23 +0200, Dmitry Adamushko wrote:
> > [...]
> > Well, it's a late hour, so maybe I'm missing something... but it does
> > look to be HZ and "will run" time interval related issue. Like
> > described in (*). Or maybe we both observe similar situations but have
> > different
On Fri, Mar 30, 2007 at 02:06:05PM -0700, [EMAIL PROTECTED] wrote:
>
> The patch titled
> Add locking to evdev
> has been added to the -mm tree. Its filename is
> add-locking-to-evdev.patch
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http:/
On Sun, 2007-04-08 at 09:08 -0400, Ed Tomlinson wrote:
> Hi,
>
> I am one of those who have been happily testing Con's patches.
>
> They work better than mainline here.
(I tried a UP kernel yesterday, and even a single kernel build would
make noticeable hitches if I move a window around. YMMV
> On Sat, 2007-04-07 at 13:08 -0700, David Brownell wrote:
> > On Friday 06 April 2007 10:01 pm, Greg KH wrote:
> >
> > > Are you _sure_ you have a 1-to-1 relationship here? No multiple devices
> > > pointing to the same acpi node? Or the other way around? If so, you
> > > are going to have to
On Monday 09 April 2007, Mike Galbraith wrote:
>On Sun, 2007-04-08 at 13:57 -0400, Gene Heskett wrote:
>> On Sunday 08 April 2007, Mike Galbraith wrote:
>> >On Sun, 2007-04-08 at 13:40 +0200, Mike Galbraith wrote:
>> >> On Sun, 2007-04-08 at 07:33 -0400, Gene Heskett wrote:
>> >> > That seems to be
On Monday 09 April 2007, Mike Galbraith wrote:
>On Sun, 2007-04-08 at 13:56 -0400, Gene Heskett wrote:
>> On Sunday 08 April 2007, Mike Galbraith wrote:
>> >On Sun, 2007-04-08 at 07:33 -0400, Gene Heskett wrote:
>> >> That seems to be the killer loading here, building a kernel (make
>> >> -j3) does
On Mon, 09 Apr 2007 00:58:53 +0200, "Richard Knutsson"
<[EMAIL PROTECTED]> said:
> Wow, I'm impressed. Think you got the record on how many mails you
> referenced to in a reply...
TWO actually. I guess you are easily impressed.
A simple cut and paste error.
> You have got some rude answers and
On Monday 09 April 2007, [EMAIL PROTECTED] wrote:
>
>I AM SURE THERE ARE A HUGE NUMBER OF PEOPLE WHO WOULD GIVE IT A TRY.
>
Many of us have, and recall the pain. We'll pass thank you.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please us
[EMAIL PROTECTED] wrote:
YOU GUYS WILL LAUGH ABOUT THIS:
Yes, we are laughing at you.
You keep using bonnie++ after being told it's a poor benchmark.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More ma
[EMAIL PROTECTED] wrote:
REISER4 FOR INCLUSION IN THE LINUX KERNEL.
Dave Lynch takes a reasoned approach to REISER4.
Dave Lynch wrote:
Jeff Garzik wrote:
If the compelling reason is that it needs a test, I'd say its not ready.
Can you please elaborate ? I am not sure I understand what you a
YOU GUYS WILL LAUGH ABOUT THIS:
I forgot the all the statistics that might support the sase for REISER4
inclusion.
Well, here it all is:
http://linuxhelp.150m.com/resources/fs-benchmarks.htm and
http://m.domaindlx.com/LinuxHelp/resources/fs-benchmarks.htm
.-.
| FILESYSTE
Eric Sandeen wrote:
Samuel Thibault wrote:
Hi,
Distribution installers usually try to probe OSes for building a suited
grub menu. Unfortunately, mounting an ext3 partition, even in read-only
mode, does perform some operations on the filesystem (log recovery).
This is not a good idea since it m
Error handling in fs/sysfs/bin.c:write() was wrong because size_t
count is used to receive return value from flush_write() which is
negative on failure.
This patch updates write() such that int variable is used instead.
read() is updated the same way for consistency.
Signed-off-by: Tejun Heo <[EM
Add sysfs_dirent->s_parent. With this patch, each sd points to and
holds a reference to its parent. This allows walking sysfs tree
without referencing sd->s_dentry which can go away anytime if the user
doesn't control when it's deleted.
sd->s_parent is initialized and parent is referenced in
sys
On Sun, 2007-04-08 at 20:51 +0200, Rene Herman wrote:
> On 04/08/2007 12:41 PM, Ingo Molnar wrote:
>
> > this is pretty hard to get right, and the most objective way to change
> > it is to do it testcase-driven. FYI, interactivity tweaking has been
> > gradual, the last bigger round of interacti
Currently there are four functions to create sysfs_dirent -
__sysfs_new_dirent(), sysfs_new_dirent(), __sysfs_make_dirent() and
sysfs_make_dirent(). Other than sysfs_make_dirent(), no function has
two users if calls to implement other functions are excluded.
This patch consolidates sysfs_dirent c
Inode number handling was incorrect in two ways.
1. sysfs uses the inode number allocated by new_inode() and never
hashes it. When reporting the inode number, it uses iunique() if
inode is inaccessible. This is incorrect because iunique() assumes
the inodes are hashed. This can cause d
On Sun, 2007-04-08 at 13:57 -0400, Gene Heskett wrote:
> On Sunday 08 April 2007, Mike Galbraith wrote:
> >On Sun, 2007-04-08 at 13:40 +0200, Mike Galbraith wrote:
> >> On Sun, 2007-04-08 at 07:33 -0400, Gene Heskett wrote:
> >> > That seems to be the killer loading here, building a kernel (make
>
kobj->dentry can go away anytime unless the user controls when the
associated sysfs node is deleted. This patch implements
kobj_sysfs_assoc_lock which protects kobj->dentry. This will be used
to maintain kobj based API when converting sysfs to use sysfs_dirent
tree instead of dentry/kobject.
Not
Make sd->s_element a union of sysfs_elem_{dir|symlink|attr|bin_attr}
and rename it to s_elem. This is to achieve...
* some level of type checking : changing symlink to point to
sysfs_dirent instead of kobject is much safer and less painful now.
* easier / standardized dereferencing
* allow sysf
Implement bin_buffer which contains a mutex and pointer to PAGE_SIZE
buffer to properly synchronize accesses to per-openfile buffer and
prepare for immediate-kobj-disconnect.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/bin.c | 64 ++-
sysfs is now completely out of driver/module lifetime game. After
deletion, a sysfs node doesn't access anything outside sysfs proper,
so there's no reason to hold onto the attribute owners. Note that
often the wrong modules were accounted for as owners leading to
accessing removed modules.
This
Opening a sysfs node references its associated kobject, so userland
can arbitrarily prolong lifetime of a kobject which complicates
lifetime rules in drivers. This patch implements active reference and
makes the association between kobject and sysfs immediately breakable.
Now each sysfs_dirent ha
Now that sysfs_dirent can be disconnected from kobject on deletion,
there is no need to orphan each attribute files. All [bin_]attribute
nodes are automatically orphaned when the parent node is deleted.
Kill attribute file orphaning.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/file
Add s_name to sysfs_dirent. This is to further reduce dependency to
the associated dentry. Name is copied for directories and symlinks
but not for attributes.
Where possible, name dereferences are converted to use sd->s_name.
sysfs_symlink->link_name and sysfs_get_name() are unused now and
remov
sysfs symlink is implemented by referencing dentry and kobject from
sysfs_dirent - symlink entry references kobject, dentry is used to
walk the tree. This complicates object lifetimes rules and is
dangerous - for example, there is no way to tell to which module the
target of a symlink belongs and
There is no reason this function should be inlined and soon to follow
sysfs object reference simplification will make it heavier. Move it
to dir.c.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/dir.c | 12
fs/sysfs/sysfs.h | 13 +
2 files changed, 13 in
Hello, all.
This is the second take of sysfs-immediate-disconnct patchset.
In the last take, rwsem was added to s_elem.dir to protect kobj only.
This wasn't enough because attr and bin_attr need to hold onto not
only the kobject of their parents but also the module backing
themselves and ops too,
Flatten cleanup paths in sysfs_add_link() and create_dir() to improve
readability and ease further changes to these functions. This is in
preparation of object reference simplification.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/dir.c | 73 ++-
On Sun, 2007-04-08 at 13:56 -0400, Gene Heskett wrote:
> On Sunday 08 April 2007, Mike Galbraith wrote:
> >On Sun, 2007-04-08 at 07:33 -0400, Gene Heskett wrote:
> >> That seems to be the killer loading here, building a kernel (make -j3)
> >> doesn't seem to lag it all that bad. One session of gzi
REISER4 FOR INCLUSION IN THE LINUX KERNEL.
Dave Lynch takes a reasoned approach to REISER4.
Dave Lynch wrote:
>
> Jeff Garzik wrote:
> >
> > If the compelling reason is that it needs a test, I'd say its not ready.
> >
>
> Can you please elaborate ? I am not sure I understand what you are
> ar
On Sun, Apr 08, 2007 at 11:22:31AM +0100, Christoph Hellwig wrote:
> On Wed, Apr 04, 2007 at 05:43:49PM +0530, Ananth N Mavinakayanahalli wrote:
> > This patch provides a debugfs knob to turn kprobes on/off
> >
> > o A new file /debug/kprobes/enabled indicates if kprobes is enabled or
> > not (d
On Monday 09 April 2007, Mike Galbraith wrote:
>On Sun, 2007-04-08 at 13:04 -0400, Gene Heskett wrote:
>> On Sunday 08 April 2007, Ingo Molnar wrote:
>> >and note that a year ago Mike did a larger patch too, not unlike his
>> >current patch - but we hoped that his smaller change would be
>> > suffi
On Sun, 2007-04-08 at 13:04 -0400, Gene Heskett wrote:
> On Sunday 08 April 2007, Ingo Molnar wrote:
> >and note that a year ago Mike did a larger patch too, not unlike his
> >current patch - but we hoped that his smaller change would be sufficient
> >- and nobody came along and said "i tested Mik
Samuel Thibault wrote:
Hm, so the root cause there seems that the installer found 2 legs of a
mirror and mounted them independently, recovering them independently...
But why did that cause problems?
Because that thrashed his data (or at least it didn't help to keep data
safe).
Other options
Eric Sandeen, le Sun 08 Apr 2007 22:24:50 -0500, a écrit :
> Samuel Thibault wrote:
> >Distribution installers usually try to probe OSes for building a suited
> >grub menu. Unfortunately, mounting an ext3 partition, even in read-only
> >mode, does perform some operations on the filesystem (log rec
Samuel Thibault wrote:
Hi,
Distribution installers usually try to probe OSes for building a suited
grub menu. Unfortunately, mounting an ext3 partition, even in read-only
mode, does perform some operations on the filesystem (log recovery).
This is not a good idea since it may silently garbage d
On Mon, Apr 02, 2007 at 10:51:27PM +0200, Pavel Machek wrote:
> > >
> > > Should we create CONFIG_FREEZER?
> >
> > Why do you think so? I think the freezer should be compiled automatically
> > if any of the above is set, which is what this directive really means.
>
> Kconfig can do that. ("sele
The option CONFIG_PACKET_MMAP should depend on MMU.
Signed-off-by: Aubrey.Li <[EMAIL PROTECTED]>
---
net/packet/Kconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/packet/Kconfig b/net/packet/Kconfig
index 34ff93f..959c272 100644
--- a/net/packet/Kconfig
+++ b/net
On Fri, Apr 06, 2007 at 11:25:00PM -0700, Andrew Morton wrote:
> On Fri, 6 Apr 2007 14:41:50 -0700 "Keshavamurthy, Anil S" <[EMAIL PROTECTED]>
> wrote:
>
> > Subject: Avoid checking for cpu gone when CONFIG_HOTPLUG_CPU not defined
> >
> > Avoid checking for cpu gone in mm hot path when
> > CONFI
On Sat, 2007-04-07 at 13:08 -0700, David Brownell wrote:
> On Friday 06 April 2007 10:01 pm, Greg KH wrote:
>
> > Are you _sure_ you have a 1-to-1 relationship here? No multiple devices
> > pointing to the same acpi node? Or the other way around? If so, you
> > are going to have to change the n
On Fri, 06 Apr 2007 17:02:58 -0700 Jeremy Fitzhardinge <[EMAIL PROTECTED]>
wrote:
>> You're too kind. wli's comment on the first version of this patch was
>> something along the lines of "this patch causes a surprising amount of
>> damage for what little it achieves".
On Fri, Apr 06, 2007 at 05:
[EMAIL PROTECTED] wrote:
On Sat, 07 Apr 2007 23:42:20 +0600, root said:
As we know that, linux scheduler use separate runqueue for every CPU of
a multiprocessor system, which having an active and an expired array.If
we use only one expired array, then the CPUs of a multiprocessor system
will be
I concur with Eric's assessment. Adding new magic bits to the generic
clone path seems like a poor way to cope with kernel threads. I think
it's better if kernel thread setup gets less like normal user process
setup. I also agree with Eric that PPID of 0 is a very natural way for
kernel threads
I think that's correct.
Thanks,
Roland
-
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/
Hi,
It seem the hid-pidff driver also should be sticky.
Good luck
- Li Yu
-
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 htt
On Sun, Apr 08, 2007 at 12:28:32PM -0700, H. Peter Anvin wrote:
> Theodore Tso wrote:
> >It doesn't state explicitly that you can use the telldir cookie()
> >after closing the directory stream using closedir() and then reopening
> >it using opendir(), but given that it states that results are
> >un
On Sat, 2007-04-07 at 19:47 -0700, Randy Dunlap wrote:
> On Sat, 07 Apr 2007 19:21:01 -0500 Larry Finger wrote:
>
> > With the following line in /etc/modprobe.conf.local:
> >
> > options bcm43xx fwpostfix = ".fw3" locale=8
> >
> > the kernel oops below is generated. I realize that the line shoul
On Fri, 2007-04-06 at 08:39 -0700, H. Peter Anvin wrote:
> I will, unless Rusty does, first. No desire to step on each other.
Oh no, please, after you!
Rusty.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> On 04/08, Eric W. Biederman wrote:
>
>> If we are going to have kernel only flags please use an additional
>> argument to do_fork and copy_process.
>
> Yes, we can do this. But we have a number of architectures which use
> sys_clone() to implement kernel
Alan Cox wrote:
The second FIXME area is ata_irq_ack - it is unconditionally coded
for SFF-type interfaces. I believe that using this function in
non-BMDMA interfaces is wrong - it attempts to read from the BMDMA
registers irrespective of whether ap->ioaddr.bmdma_addr is set or
not. The questio
Andrew Morton wrote:
netdev:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/broken-out/forcedeth-work-around-null-skb-dereference-crash.patch
It sounded this was specific to Ingo. I haven't heard anybody else
complain, and AFAIK Ayaz and Ingo were sti
[AGPGART] intel: Add 965GM chipset support
Update PCI id info for Intel 965GM chipset.
Signed-off-by: Wang Zhenyu <[EMAIL PROTECTED]>
---
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index e542a62..a9fdbf9 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/
On Sun, Apr 08, 2007 at 04:09:54PM -0700, Andrew Morton wrote:
>
> I'm sitting on five patches which look like 2.6.21 material, but which
> would normally go through subsystem maintainers:
>
> driver core:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm
[...]
Well, it's a late hour, so maybe I'm missing something... but it does
look to be HZ and "will run" time interval related issue. Like
described in (*). Or maybe we both observe similar situations but have
different reasons behind them.
I meant that account_user_time() is also called from ti
On 08/04/07, Mike Galbraith <[EMAIL PROTECTED]> wrote:
On Sat, 2007-04-07 at 19:17 +0200, Mike Galbraith wrote:
> I lowered the time to 500us, and ran at nice -10.. it starves tenpercent
> here every time. (ran as taskset -c 1 nice -n -10 ./fairtest) The
> starving 10% duty cycle task has trou
On 4/8/07, JanuGerman <[EMAIL PROTECTED]> wrote:
Hi every one,
I have one question regarding security libraries, already shipped with Linux
Kernel. That is, all PKI, RSA libraries, as provided by OpenSSL are already
integrated within the linux kernel source code? OR, one have to use OpenSSL
s
Hi,
Distribution installers usually try to probe OSes for building a suited
grub menu. Unfortunately, mounting an ext3 partition, even in read-only
mode, does perform some operations on the filesystem (log recovery).
This is not a good idea since it may silently garbage data. XFS has a
norecover
On Thu, 5 Apr 2007 19:50:11 -0700 (PDT) Linus Torvalds <[EMAIL PROTECTED]>
wrote:
>
> Ok,
> I don't think there really is anything very interesting here, but we're
> hopefully whittling down the list of regressions, and fixing various
> random other small issues while at it.
>
> Some smallis
Wow, I'm impressed. Think you got the record on how many mails you
referenced to in a reply... But dude, please calm down, the caps-lock is
not the answer. You have got some rude answers and you have called them
back on it + you have repeated the same statement several times, that is
not the be
Christer Weinigel: Until YOU, have actually used the REISER4 filesystem
yourself, I think YOU OWE IT to the people on the linux-kernel mailing
list, to, AS YOU SAY, shut the fuck up.
Even reading up on the REISER4 filesystem would help.
Applying a little intelligence would undoubtedly help too
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc6/2.6.21-rc6-mm1/
- Lots of x86 updates
- This is a 25MB diff against mainline, which is rather large.
Boilerplate:
- See the `hot-fixes' directory for any important updates to this patchset.
- To fetch an -mm tree usin
Hi.
On Sun, 2007-04-08 at 18:47 +0200, Rafael J. Wysocki wrote:
> On Sunday, 8 April 2007 01:42, Nigel Cunningham wrote:
> > Hi.
> >
> > On Sun, 2007-04-08 at 01:13 +0200, Rafael J. Wysocki wrote:
> > > On Sunday, 8 April 2007 00:31, Nigel Cunningham wrote:
> > > > Hi.
> > > >
> > > > On Sat, 20
On Tue, 3 Apr 2007 15:55:32 +0200 (CEST) Bernhard Kaindl <[EMAIL PROTECTED]>
wrote:
> With at least 3 of the following 4 patches, s2ram and s2disk are
> fixed on at least the Acer Ferrari 1000 notebooks and at least
> s2disk on the Acer Ferrari 5000 notebooks.
These patches cause my Vaio to oops
On Sat, Apr 07, 2007 at 04:36:33PM -0400, Theodore Tso wrote:
> 1) Deprecate telldir/seekdir() altogether. Relatively few progams use
> this functionality, and it is highly questionable how useful it is,
> anyway. If you use telldir/seekdir and keep the cookie for a long
> time, even the POSIX-pr
Please reproduce and provide a new crash dump without the nvidia
binary-only module loaded.
Hi again,
Here is a new crash dump (I also removed vmnet and vmmon properitary
modules), this time I also included a lspci output:
Apr 8 21:47:21 localhost pppd[2114]: rcvd [proto=0xfc3b] bc d4 80 eb
4
On Tue, 3 Apr 2007 16:00:36 +0200 (CEST) Bernhard Kaindl <[EMAIL PROTECTED]>
wrote:
> --- linux-2.6.20.orig/arch/i386/kernel/smpboot.c
> +++ linux-2.6.20/arch/i386/kernel/smpboot.c
> @@ -59,6 +59,7 @@
> #include
> #include
> #include
> +#include
>
This inclusion breaks `make headers_chec
> + /*
> + * DMA is based on a 16MHz clock
> + */
> + if (ata_timing_compute(adev, adev->dma_mode, &t, 1000, 1))
> + return;
This seems strange for a 16MHz clock.
> +
> + /*
> + * Now, properly adjust the timings. If we have a 62.5ns clock
> + * period
On Sun, 2007-04-08 at 10:33 +0200, Thomas Gleixner wrote:
>
> Oh well, this is a leftover from the days where we tried to use TSC
> despite of frequency changes. It still modifies the scale factor of the
> tsc clocksource.
>
> I agree that it can be removed as we switch off TSC anyway in that ca
Alex Dubov wrote:
> Problem 2: After a data crc error all subsequent commands fail. May it be
> caused by stop command
> leaving card in some bad state (something clearable by SEND_STATUS)? On the
> other hand, is there a
> real need to issue a stop command in case main command failed?
>
It mig
On 4/8/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
More fundamentally, the telldir cookie should never be valid when
applied to a different DIR * (even one that refers to the same directory.)
Don't worry about this. This is clearly the semantics which was
always wanted. I've filed a defect r
Alex Dubov wrote:
> Recently, I've obtained a bug report concerning an MMC card. Two problems are
> described, both
> sporadic.
> Problem 1: illegal ocr value is returned. You may notice, in the non-working
> case, obviously
> incorrect ocr value (0x) is returned. The card won't work afte
From: Arnd Bergmann <[EMAIL PROTECTED]>
Date: Sun, 8 Apr 2007 16:51:20 +0200
> On Sunday 08 April 2007, Christoph Hellwig wrote:
> >
> > Now that there is no arch-specific compat ioctl handling left there
> > is not point in having a separate copat_ioctl.h, so merge it into
> > compat_ioctl.c
>
Philip Langdale wrote:
> Fix handling of low voltage MMC cards.
>
>
Sorry, my fifo filled up and you got stuck at the far end.
I've applied this and will push to andrew in a bit.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core de
Theodore Tso wrote:
It doesn't state explicitly that you can use the telldir cookie()
after closing the directory stream using closedir() and then reopening
it using opendir(), but given that it states that results are
undefined after a rewinddir() --- which is much less violent than a
closedir()
On 4/8/07, Theodore Tso <[EMAIL PROTECTED]> wrote:
Ulrich, is it too late to insert a clarification that the telldir()
cookie isn't guaranteed to be valid after closedir() *or* rewinddir()?
It's never too late.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
Chris Wright wrote:
Arnaldo Carvalho de Melo (1):
DCCP: Fix exploitable hole in DCCP socket options
Does this fix cure CVE-2007-1730 and CVE-2007-1734, or just one of them?
They both seem to be in the exact same code path the patch touches.
-
To unsubscribe from this list: send the li
On Sun, Apr 08, 2007 at 08:41:30PM +0200, Jörn Engel wrote:
>
> Garbage-collecting them on closedir() does not work. It surprised me as
> well, but there seem to be applications that keep the telldir() cookie
> around after closedir(). Iirc, "rm -r" was one of them.
>
> Neil, is this correct?
Theodore Tso wrote:
You could, but then you're succeptible to a memory allocation attack.
If you have an arbitrarily large directory (say, one with multiple
millions of entries), and the attacker program calls seekdir() after
every single readdir() call, you would then force the kernel to
alloca
On Mon, 02 Apr 2007 10:35:40 +0200, Rene Rebe said:
(Sorry for the late reply..)
> IIRC a MSI Megabook S270 (I formerly owned) BIOS notifies this
> "Critical temperature reached (128C)" when the battery run empty
> when the OS did no action due to battery low indications. I guess
> the BIOS peopl
> The second FIXME area is ata_irq_ack - it is unconditionally coded
> for SFF-type interfaces. I believe that using this function in
> non-BMDMA interfaces is wrong - it attempts to read from the BMDMA
> registers irrespective of whether ap->ioaddr.bmdma_addr is set or
> not. The question this p
On 04/08/2007 12:41 PM, Ingo Molnar wrote:
this is pretty hard to get right, and the most objective way to change
it is to do it testcase-driven. FYI, interactivity tweaking has been
gradual, the last bigger round of interactivity changes were done a year
ago:
commit 5ce74abe788a26698876e66
On 4/7/07, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
It's not going to solve anything at all. We can't stop supporting
functionality that has been there forever.
Not necessarily.
One problem here is that the interface for using readdir() with and
without telldir()/seekdir() is the same. A
On Sun, Apr 08, 2007 at 11:11:20AM -0700, H. Peter Anvin wrote:
> Christoph Hellwig wrote:
> >On Sat, Apr 07, 2007 at 04:36:33PM -0400, Theodore Tso wrote:
> >>this functionality, and it is highly questionable how useful it is,
> >>anyway. If you use telldir/seekdir and keep the cookie for a long
On Sun, 8 April 2007 11:11:20 -0700, H. Peter Anvin wrote:
>
> Well, the question is if you can keep the seekdir/telldir cookie around
> as a pointer -- preferrably in userspace, of course. You would
> presumably garbage-collect them on closedir() -- there is no other point
> at which you coul
Gidday,
After a long hiatus, a new man-pages release...
And a happy announcement! My work on man-pages is now partially supported
by my employer, Google. Henceforth, something up to 20% [*] of my working
week (depending on other time pressures...) will be spent on man-pages
maintenance. Thanks
[Adding linux-kernel to the cc list, hoping for wider exposure.]
On Fri, 23 Mar 2007 20:08:17 -0500
Jay Cliburn <[EMAIL PROTECTED]> wrote:
> We're trying to track down the source of a problem that occurs
> whenever the atl1 network driver is activated on a 32-bit 2.6.21-rc4
and -rc5, -rc6, 2.6.2
Mike Galbraith wrote:
> On Sat, 2007-04-07 at 19:17 +0200, Mike Galbraith wrote:
> > I lowered the time to 500us, and ran at nice -10.. it starves tenpercent
> > here every time. (ran as taskset -c 1 nice -n -10 ./fairtest) The
> > starving 10% duty cycle task has trouble getting 1% CPU.
>
> Hmm.
worker_thread() can miss freeze_process()->signal_wake_up() if it happens
between try_to_freeze() and prepare_to_wait(). We should check freezing()
before entering schedule().
This race was introduced by me in
[PATCH 1/1] workqueue: don't migrate pending works from the dead CPU
Looks lik
We already depend on fact that all sub-threads have ->exit_signal == -1,
no need to set it in zap_other_threads().
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- 2.6.21-rc5-mm4/kernel/signal.c~zat 2007-04-07 20:11:14.0 +0400
+++ 2.6.21-rc5-mm4/kernel/signal.c 2007-04-08 22:09:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theodore Tso wrote:
> The reason why I ignore the tar+gzip tests is that in the past Hans
> has rigged the test by using a tar ball which was generated by
> unpacking a set of kernel sources on a reiser4 filesystem, and then
> repacking them using tar+
Christoph Hellwig wrote:
On Sat, Apr 07, 2007 at 04:36:33PM -0400, Theodore Tso wrote:
this functionality, and it is highly questionable how useful it is,
anyway. If you use telldir/seekdir and keep the cookie for a long
time, even the POSIX-provided guarantees about files that are created
and
vjn wrote:
in my project i want to code the kernel such that when i plugged my usb it
should ask for password and check it in the kernel space . can anyone help
me
I think the correct solution is to use an excrypted mount, and issue the
mount command manually with the question in user space. T
On Sunday 08 April 2007, Mike Galbraith wrote:
>On Sun, 2007-04-08 at 13:40 +0200, Mike Galbraith wrote:
>> On Sun, 2007-04-08 at 07:33 -0400, Gene Heskett wrote:
>> > That seems to be the killer loading here, building a kernel (make
>> > -j3) doesn't seem to lag it all that bad. One session of gz
1 - 100 of 152 matches
Mail list logo
