-stable review patch. If anyone has any objections, please let us know.
--
From: Albert Lee <[EMAIL PROTECTED]>
libata: Clear tf before doing request sense (take 3)
patch 2/4:
Clear tf before doing request sense.
This fixes the AOpen 56X/AKH timeout problem.
-stable review patch. If anyone has any objections, please let us know.
--
From: Andrew Morton <[EMAIL PROTECTED]>
Revert e92a4d595b464c4aae64be39ca61a9ffe9c8b278.
Dmitry points out
"When we block_prepare_write() failed while ext3_prepare_write() we jump to
"failure" label
-stable review patch. If anyone has any objections, please let us know.
--
From: Andrew Morton <[EMAIL PROTECTED]>
Revert b46be05004abb419e303e66e143eed9f8a6e9f3f. Same reasoning as for ext3.
Cc: Kirill Korotaev <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Ken
-stable review patch. If anyone has any objections, please let us know.
--
From: John W. Linville <[EMAIL PROTECTED]>
[PATCH] softmac: avoid assert in ieee80211softmac_wx_get_rate
Unconfigured bcm43xx device can hit an assert() during wx_get_rate
queries. This is because
-stable review patch. If anyone has any objections, please let us know.
--
From: Conke Hu <[EMAIL PROTECTED]>
ahci.c: walkaround for SB600 SATA internal error issue
There is a HW issue in ATI SB600 SATA that PxSERR.E should not be
set on some conditions, for example, when
-stable review patch. If anyone has any objections, please let us know.
--
Update libata drive blacklist to the latest from 2.6.21
Removes one duplicate entry from blacklist table, adds several
entries for drives with broken NCQ.
[diff between 2.6.20 and 2.6.21-rc6, with one
-stable review patch. If anyone has any objections, please let us know.
--
From: Mark Lord <[EMAIL PROTECTED]>
2.6.21 fix lba48 bug in libata fill_result_tf()
Current 2.6.21 libata does the following:
void ata_tf_read(struct ata_port *ap, struct ata_taskfile *tf)
{
-stable review patch. If anyone has any objections, please let us know.
--
From: Stephen Hemminger <[EMAIL PROTECTED]>
This adds working recovery from transmit timeouts. Previous code
didn't do enough to truly reset chip.
It is a backport of the 2.6.21 code.
Signed-off-by:
-stable review patch. If anyone has any objections, please let us know.
--
From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
[IPv6]: Fix incorrect length check in rawv6_sendmsg()
In article <[EMAIL PROTECTED]> (at Thu, 29 Mar 2007 14:26:44 -0700 (PDT)),
David Miller <[EMAIL
-stable review patch. If anyone has any objections, please let us know.
--
From: Mark Lord <[EMAIL PROTECTED]>
libata bugfix: preserve LBA bit for HDIO_DRIVE_TASK
Preserve the LBA bit in the DevSel/Head register for HDIO_DRIVE_TASK.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
-stable review patch. If anyone has any objections, please let us know.
--
From: David Miller <[EMAIL PROTECTED]>
[SCSI]: Fix scsi_send_eh_cmnd scatterlist handling
This fixes a regression caused by commit:
2dc611de5a3fd955cd0298c50691d4c05046db97
The sense buffer code in
-stable review patch. If anyone has any objections, please let us know.
--
From: Stephen Hemminger <[EMAIL PROTECTED]>
Driver needs to turn off carrier when down, otherwise it can
confuse bonding and bridging and looks like carrier is on immediately
when it is brought back up.
-stable review patch. If anyone has any objections, please let us know.
--
From: Patrick McHardy <[EMAIL PROTECTED]>
[NETFILTER]: ipt_CLUSTERIP: fix oops in checkentry function
The clusterip_config_find_get() already increases entries reference
counter, so there is no reason to
-stable review patch. If anyone has any objections, please let us know.
--
From: Thomas Gleixner <[EMAIL PROTECTED]>
The __copy_to_user_inatomic() calls in file_read_actor() and pipe_read()
are broken on original i386 machines, where WP-works-ok == false, as
-stable review patch. If anyone has any objections, please let us know.
--
From: Andreas Oberritter <[EMAIL PROTECTED]>
DVB: tda10086: fix DiSEqC message length
Setting the message length to zero means to send one byte, so you need a
subtraction instead of an addition.
(cherry
This is the start of the stable review cycle for the 2.6.20.7 release.
There are 31 patches in this series, all will be posted as a response to
this one. If anyone has any issues with these being applied, please let
us know. If anyone is a maintainer of the proper subsystem, and wants
to add a
-stable review patch. If anyone has any objections, please let us know.
--
From: Jan Beulich <[EMAIL PROTECTED]>
Commit 2e3646e51b2d6415549b310655df63e7e0d7a080 changed the way
the split config tree is built, but failed to also adjust fixdep
accordingly - if changing a config
Roland Dreier wrote:
> BTW: any idea how this ever got triggered? The only way I can see is
> if you're either not using libipathverbs and libibverbs and you just
> create the CQ some other way, which seems unlikely. Do you know how
> Jason triggered this bug?
Yes, it was because he was
On Wed, 2007-04-11 at 15:21 -0400, Mathieu Desnoyers wrote:
> * Andrew Morton ([EMAIL PROTECTED]) wrote:
> > On Wed, 11 Apr 2007 13:51:11 -0400
> > Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> >
> > > > What's this marker stuff about?
> > > >
> > >
> > > Hi Russel,
> > >
> > > Here is an
Rik van Riel a écrit :
Make it possible for applications to have the kernel free memory
lazily. This reduces a repeated free/malloc cycle from freeing
pages and allocating them, to just marking them freeable. If the
application wants to reuse them before the kernel needs the memory,
not even a
On Thu, 12 Apr 2007 00:14:59 +0200
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Andrew Morton napisa__(a):
> > On Wed, 11 Apr 2007 20:03:17 +0200
> > Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> >
> >> [EMAIL PROTECTED] napisa__(a):
> >>> The mm snapshot broken-out-2007-04-11-02-24.tar.gz
On Thu, 12 Apr 2007, Neil Brown wrote:
For the second.
You say that you " would need at least 96 bits in order to make that
guarantee; 64 bits of hash, plus a 32-bit count value in the hash
collision chain". I think 96 is a bit greedy. Surely 48 bits of
hash and 16 bits of
> 2) How should an application be written to not be killed by OOM?
OOM isn't an application matter. The kernel has to choose between
allowing overcommit on the basis it might run out of memory and have to
kill stuff, or that it won't in which case an applicatio which correctly
handles malloc()
On Wednesday April 11, [EMAIL PROTECTED] wrote:
> On Wed, Apr 11, 2007 at 07:15:57AM +1000, Neil Brown wrote:
> > > Neil, is this correct?
> >
> > It's just NFS. nfsd does open/getdents/close on every readdir
> > request.
>
> That's... unfortunate.
I like to think of it as "challenging" :-)
>
> BTW: any idea how this ever got triggered? The only way I can see is
> if you're either not using libipathverbs and libibverbs and you just
> create the CQ some other way, which seems unlikely. Do you know how
> Jason triggered this bug?
Yes, it was because he was using 32-bit userspace
On Wed, 11 Apr 2007 14:17:04 +0800
"Zhao Forrest" <[EMAIL PROTECTED]> wrote:
> We're using RHEL5 with kernel version 2.6.18-8.el5.
> When doing a stress test on raw device for about 3-4 hours, we found
> the soft lockup message in dmesg.
> I know we're not reporting the bug on the latest kernel,
On Wednesday 11 April 2007 16:48, Willy Tarreau wrote:
> On Wed, Apr 11, 2007 at 02:23:31AM -0300, Pedro wrote:
> > After suffering some days from a not|mis configured tmpfs,
> >
> > As the OOM killer is not Posix,
> >
> > Better than to kill processes would be to resize tmpfs, to use tmpfs
Roland Dreier wrote:
I just queued all of this for 2.6.22.
Is there any chance of getting a fix for the use-after-free that can
be caused by allocating something from userspace, failing to mmap the
buffer and then exiting? To see what happens, look at how
ipath_create_cq sticks a struct
Andrew Morton napisał(a):
> On Wed, 11 Apr 2007 20:03:17 +0200
> Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>
>> [EMAIL PROTECTED] napisa__(a):
>>> The mm snapshot broken-out-2007-04-11-02-24.tar.gz has been uploaded to
>>>
>>>
>>>
Jan Engelhardt wrote:
> On Apr 11 2007 17:35, Chuck Ebbert wrote:
>> Jan Engelhardt wrote:
>>> On Apr 11 2007 17:07, Chuck Ebbert wrote:
When I reboot my notebook, it powers off and powers back on.
On poweroff a loud snapping noise seems to be coming from the
hard drive. Today I
On Wed, 11 Apr 2007 01:00:17 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Should we copy Andrew or is someone else going to collect up all of these
> patches?
Andrew is cowering in terror, because utrace goes tromping through this
code.
It would be rather good to get utrace moving
From: Randy Dunlap <[EMAIL PROTECTED]>
Johannes Berg reported that struct names are not highlighted
(bold, italic, etc.) in html kernel-doc output. (Also not in
text-mode output, but I don't see that changing.)
This patch adds the following:
- highlight struct names in html output mode
-
A while back, Christoph mentioned that he thought that iunique ought to be
cleaned up to use a more conventional loop construct. This patch does that,
turning the strange goto loop into a do/while.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
diff --git a/fs/inode.c b/fs/inode.c
index
On Apr 11 2007 17:35, Chuck Ebbert wrote:
>Jan Engelhardt wrote:
>> On Apr 11 2007 17:07, Chuck Ebbert wrote:
>>> When I reboot my notebook, it powers off and powers back on.
>>> On poweroff a loud snapping noise seems to be coming from the
>>> hard drive. Today I noticed there is no "shutdown:
On Mon, 26 Mar 2007, Dmitry Torokhov wrote:
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
I don't think that you need to concern yourself with this too much
at present. If X11 people (e.g. Kristian) present evidence that kernel
fails to deliver an event, then we'll look at it. However it
Jan Engelhardt wrote:
> On Apr 11 2007 17:07, Chuck Ebbert wrote:
>> When I reboot my notebook, it powers off and powers back on.
>> On poweroff a loud snapping noise seems to be coming from the
>> hard drive. Today I noticed there is no "shutdown: hda" on
>> the console when I reboot. Whne I do a
On Wed, 11 Apr 2007 13:54:41 -0700
Daniel Walker <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-04-11 at 13:31 -0700, Andrew Morton wrote:
> > On Wed, 11 Apr 2007 09:29:04 -0700
> > Daniel Walker <[EMAIL PROTECTED]> wrote:
> >
> > > The locking of the xtime_lock around the cpu notifier is unessesary
Eric W. Biederman wrote:
Bill Davidsen <[EMAIL PROTECTED]> writes:
As long as the original parent is preserved for getppid(). There are programs
out there which communicate between the parent and child with signals, and if
the original parent dies, it undesirable to have the child getppid()
Gene> Humm, interesting John. Neither yumex, or smart, is offering it
Gene> to me as an installable rpm for FC6.
Go and grab it from http://www.bacula.org, I'm pretty sure there are
RPMs available on there. You might also need to install seperate RPMs
for the follwoing packages:
On Wednesday 11 April 2007, John Stoffel wrote:
>> "Gene" == Gene Heskett <[EMAIL PROTECTED]> writes:
>
>Gene> Does Bacula not use tar for its dirty work?
>
>Nope, it uses it's own filesystem walking code.
>
>John
Humm, interesting John. Neither yumex, or smart, is offering it to me as
an
On Apr 11 2007 17:07, Chuck Ebbert wrote:
>
>When I reboot my notebook, it powers off and powers back on.
>On poweroff a loud snapping noise seems to be coming from the
>hard drive. Today I noticed there is no "shutdown: hda" on
>the console when I reboot. Whne I do a normal poweroff the
>message
Andrew Morton napsal(a):
> On Wed, 11 Apr 2007 22:37:03 +0200
> Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> Jiri Slaby napsal(a):
>>> Side note, as Danny wrote, there is an asus-laptop driver sitting in -mm,
>>> which supersedes this one -- if you plan to push it upstream in the near
>>> future,
When I reboot my notebook, it powers off and powers back on.
On poweroff a loud snapping noise seems to be coming from the
hard drive. Today I noticed there is no "shutdown: hda" on
the console when I reboot. Whne I do a normal poweroff the
message is displayed and there is no noise. Should the
On Wed, 11 Apr 2007 22:37:03 +0200
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> Jiri Slaby napsal(a):
> > Side note, as Danny wrote, there is an asus-laptop driver sitting in -mm,
> > which supersedes this one -- if you plan to push it upstream in the near
> > future, don't bother with this patch.
>
Can someone describe the process of finding the best value to tune the
overcommit_ratio to?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Willy Tarreau
Sent: Wednesday, April 11, 2007 3:48 PM
To: Pedro
Cc: linux-kernel@vger.kernel.org
Subject: Re: tmpfs
On Wed, 2007-04-11 at 13:31 -0700, Andrew Morton wrote:
> On Wed, 11 Apr 2007 09:29:04 -0700
> Daniel Walker <[EMAIL PROTECTED]> wrote:
>
> > The locking of the xtime_lock around the cpu notifier is unessesary now. At
> > one
> > time the tsc was used after a frequency change for timekeeping,
Milind Arun Choudhary wrote:
> SPIN_LOCK_UNLOCKED cleanup,use DEFINE_SPINLOCK instead
Committed to linux1394-2.6.git. Thanks,
--
Stefan Richter
-=-=-=== -=-- -=-==
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 11 Apr 2007 21:42:27 +0200
Helge Hafting <[EMAIL PROTECTED]> wrote:
> 2.6.21-rc6-mm1 locks up during boot.
> The last message is:
> usbcore: registered new interface driver hiddev
>
> Then it hangs so hard that not even sysrq+B have any effect.
>
> With 2.6.18-rc5-mm1, the next messages
for arch/arm/kernel/smp.c
static DEFINE_PER_CPU(struct ipi_data, ipi_data) = {
will give a struct with name per_cpu__ipi_data
so I did
- .lock = SPIN_LOCK_UNLOCKED,
+ .lock = __SPIN_LOCK_UNLOCKED(per_cpu__ipi_data.lock),
but this dosen't seem to be the right thing to do..
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Wed, 11 Apr 2007 13:51:11 -0400
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > > What's this marker stuff about?
> > >
> >
> > Hi Russel,
> >
> > Here is an overview :
>
> I am told that the systemtap developers plan to (or are) using this
Jiri Slaby napsal(a):
> Side note, as Danny wrote, there is an asus-laptop driver sitting in -mm,
> which supersedes this one -- if you plan to push it upstream in the near
> future, don't bother with this patch.
Hmm, there is a 0.40 version in -rc6 yet. There is something weird with me
today.
Andrew Morton napsal(a):
> On Wed, 11 Apr 2007 15:04:35 +0200 (CEST)
> Jiri Slaby <[EMAIL PROTECTED]> wrote:
>
>> @@ -706,6 +718,8 @@ static int get_lcd_state(void)
>> {
>> int lcd = 0;
>>
>> +BUG_ON(!hotk->methods->lcd_status);
>
> mutter. We could just warn-and-bale here.
>
>
On Wed, 11 Apr 2007 09:29:04 -0700
Daniel Walker <[EMAIL PROTECTED]> wrote:
> The locking of the xtime_lock around the cpu notifier is unessesary now. At
> one
> time the tsc was used after a frequency change for timekeeping, but the
> re-write
> of timekeeping no longer uses the TSC unless the
No functional changes ..
I created sched_clock_drift_adjust() which holds similar code from
different places in the scheduler which all appear to do the same thing.
I also added an explicit ifdef on CONFIG_SMP, the comments seemed to
suggest it wasn't needed, but it can't hurt to make it
> "Gene" == Gene Heskett <[EMAIL PROTECTED]> writes:
Gene> Does Bacula not use tar for its dirty work?
Nope, it uses it's own filesystem walking code.
John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Eric Sandeen wrote:
Phillip Susi wrote:
Eric Sandeen wrote:
In that case you are mounting the same filesystem uner 2 different
operating systems simultaneously, which is, and always has been, a
recipe for disaster. Flagging the fs as "mounted already" would
probably be a better solution,
On 04/11, Bill Davidsen wrote:
>
> Oleg Nesterov wrote:
> >On 04/10, Eric W. Biederman wrote:
> >
> >>I'm trying to remember what the story is now. There is a nasty
> >>race somewhere with reparenting, a threaded parent setting SIGCHLD to
> >>SIGIGN, and non-default signals that results in an
On Wed, 11 Apr 2007 15:04:35 +0200 (CEST)
Jiri Slaby <[EMAIL PROTECTED]> wrote:
> @@ -706,6 +718,8 @@ static int get_lcd_state(void)
> {
> int lcd = 0;
>
> + BUG_ON(!hotk->methods->lcd_status);
mutter. We could just warn-and-bale here.
Hopefully this is just an is-jiri-sane
On Wed, Apr 11, 2007 at 01:32:19PM -0400, Jay Estabrook wrote:
> Yes, it does leak, and yes, it should be kmalloced. Something like this?
>
> struct resource *new_vga;
>
> new_vga = kmalloc(sizeof(struct resource), GFP_ATOMIC);
> if (new_vga) {
> *new_vga =
On Wed, Apr 11, 2007 at 09:10:32PM +0100, David Howells wrote:
> J. Bruce Fields <[EMAIL PROTECTED]> wrote:
>
> > Just curious--when is the actual crypto done? There doesn't seem to be
> > any in this patch.
>
> See AF_RXRPC patch:
>
>
Bill Davidsen <[EMAIL PROTECTED]> writes:
> As long as the original parent is preserved for getppid(). There are programs
> out there which communicate between the parent and child with signals, and if
> the original parent dies, it undesirable to have the child getppid() and start
> sending
J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> Just curious--when is the actual crypto done? There doesn't seem to be
> any in this patch.
See AF_RXRPC patch:
http://people.redhat.com/~dhowells/rxrpc/04-af_rxrpc.diff
You turn on CONFIG_RXKAD and load the rxkad module thus built
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> Ah yes, we still need to export kthreadd_task... I just worried about subtle
> dependency this patch adds... This "kthreadd_task = find_task_by_pid" assumes
> that init/main.c:init() takes lock_kernel() before the first kthread_create().
There is a
On Wed, Apr 11, 2007 at 12:52:56PM -0700, Zach Brown wrote:
> I'm worried that virtual aliasing spells doom for the current
> home-brewed serialization that fs/aio.c is doing with the shared ring
> head/tail accesses. Am I worrying about nothing here?
Adding a flush_dcache_page() should fix
Oleg Nesterov wrote:
On 04/10, Eric W. Biederman wrote:
I'm trying to remember what the story is now. There is a nasty
race somewhere with reparenting, a threaded parent setting SIGCHLD to
SIGIGN, and non-default signals that results in an zombie that no one
can wait for and reap. It
On Wed, 11 Apr 2007 09:55:18 -0400
Joseph Fannin <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-04-10 at 15:00 -0400, Reiner Sailer wrote:
> > Joseph,
> >
> > we cannot reproduce the BUG you report. We have identified a potential
> > source (spinlock around mutex_init). I have attached a small patch
> > I kept on getting requests from application developers who want that
> > feature. My initial patch was dated back May 2004.
>
> The right way to do it involves synchronization between the kernel side
> io_getevents() and the userspace code pulling events out of the ring.
> Alan Cox
On Wed, Apr 11, 2007 at 02:23:31AM -0300, Pedro wrote:
> After suffering some days from a not|mis configured tmpfs,
>
> As the OOM killer is not Posix,
>
> Better than to kill processes would be to resize tmpfs, to use tmpfs empty
> space.
Will not work, because tmpfs does not use any
Hi!
> I hope you like it. :)
Well, more or less... but you need signed-off-by line, and
> @@ -70,6 +70,16 @@
> * malformed UTF sequences represented as sequences of replacement glyphs,
> * original codes or '?' as a last resort if replacement glyph is undefined
> * by Adam Tla/lka <[EMAIL
2.6.21-rc6-mm1 locks up during boot.
The last message is:
usbcore: registered new interface driver hiddev
Then it hangs so hard that not even sysrq+B have any effect.
With 2.6.18-rc5-mm1, the next messages I normally get are:
usbcore: registered new interface driver usbhid
On 04/11, Eric W. Biederman wrote:
>
> Oleg Nesterov <[EMAIL PROTECTED]> writes:
>
> > On 04/11, Eric W. Biederman wrote:
> >>
> >> @@ -435,8 +436,12 @@ static void __init setup_command_line(char
> >> *command_line)
> >> static void noinline rest_init(void)
> >>__releases(kernel_lock)
> >>
On Wed, Apr 11, 2007 at 12:28:26PM -0700, Ken Chen wrote:
> >I have mixed feelings. I think the userspace getevents support was
> >poorly designed and the simple fact that we've gone this long without it
> >says just how desperately the feature isn't needed.
>
> I kept on getting requests from
> >I have mixed feelings. I think the userspace getevents support was
> >poorly designed and the simple fact that we've gone this long without it
> >says just how desperately the feature isn't needed.
>
> I kept on getting requests from application developers who want that
> feature. My initial
On Mittwoch, 11. April 2007, Jiri Slaby wrote:
> Danny Kukawka napsal(a):
> > Btw. looks as if a new version of the driver (v0.41) is already in the
> > mm-tree.
>
> Good to hear, I've got a look only to .21-rc6-mm1, where are no changes like
> this (there is 0.30).
found in the latest mm
Oleg Nesterov <[EMAIL PROTECTED]> writes:
> On 04/11, Eric W. Biederman wrote:
>>
>> @@ -435,8 +436,12 @@ static void __init setup_command_line(char
>> *command_line)
>> static void noinline rest_init(void)
>> __releases(kernel_lock)
>> {
>> +int pid;
>> kernel_thread(init,
On Wednesday 11 April 2007, Jan Engelhardt wrote:
>On Apr 10 2007 23:54, Gene Heskett wrote:
>So fix tar to not do silly things.
>Kernel major:minor numbers are not stable.
YOU Tell that to the tar/star people, they are flabbergasted that its
not stable. It apparently is for
On Wednesday 11 April 2007, John Stoffel wrote:
>> "Jan" == Jan Engelhardt <[EMAIL PROTECTED]> writes:
>
>Jan> On Apr 10 2007 23:54, Gene Heskett wrote:
>> So fix tar to not do silly things.
>> Kernel major:minor numbers are not stable.
>
> YOU Tell that to the tar/star people,
After suffering some days from a not|mis configured tmpfs,
As the OOM killer is not Posix,
Better than to kill processes would be to resize tmpfs, to use tmpfs empty
space.
I'm using kernel 2.6.20.4. If someone ask I'll send a test application.
-
To unsubscribe from this list: send the
On Wed, Apr 11, 2007 at 08:10:37PM +0100, David Howells wrote:
> Add security support to the AFS filesystem. Kerberos IV tickets are
> added as RxRPC keys are added to the session keyring with the klog
> program. open() and other VFS operations then find this ticket with
> request_key() and
On Wednesday, 11 April 2007 16:36, Oleg Nesterov wrote:
> On 04/11, Gautham R Shenoy wrote:
> > On Wed, Apr 11, 2007 at 03:48:05PM +0400, Oleg Nesterov wrote:
> > > On 04/11, Gautham R Shenoy wrote:
> > > >
> > > > On Wed, Apr 11, 2007 at 12:13:34PM +0200, Rafael J. Wysocki wrote:
> > > > >
> > >
> Ken uses the other (superior!) way of implementing ringbuffers: the head
> and tail pointers (the naming of which AIO appears to have reversed) are
> not constrained to the ringsize - they are simply allowed to wrap through
> 0xfff.
A-ha! That sure sounds great.
I'd be happy to see the
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Wed, 11 Apr 2007 13:51:11 -0400
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > > What's this marker stuff about?
> > >
> >
> > Hi Russel,
> >
> > Here is an overview :
>
> I am told that the systemtap developers plan to (or are) using this
On 04/11, Eric W. Biederman wrote:
>
> @@ -435,8 +436,12 @@ static void __init setup_command_line(char *command_line)
> static void noinline rest_init(void)
> __releases(kernel_lock)
> {
> + int pid;
> kernel_thread(init, NULL, CLONE_FS | CLONE_SIGHAND);
>
On 4/11/07, Zach Brown <[EMAIL PROTECTED]> wrote:
First, I'll NAK this and all AIO patches until the patch description
says that it's been run through the regression tests that we've started
collecting in autotest. They're trivial to run, never fear:
OK. I will run those regression tests.
Maxim Uvarov a écrit :
Eric Dumazet wrote:
>Please check kernel/sys.c:k_getrusage() to see how getrusage() has to
sum *lot* of individual fields to get precise process numbers (even
counting stats for dead threads)
Thanks for helping me and for this link. But it is not enough clear for
On Wednesday, 11 April 2007 00:20, Venki Pallipadi wrote:
> On Mon, Apr 09, 2007 at 07:40:52PM +0200, Rafael J. Wysocki wrote:
> > On Monday, 9 April 2007 18:14, Pallipadi, Venkatesh wrote:
> > >
> > > >-Original Message-
> > > >From: Rafael J. Wysocki [mailto:[EMAIL PROTECTED]
> > >
On Wed, 11 Apr 2007 12:27:59 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> + strcpy(tsk->comm, "kthreadd");
We have this dopey set_task_comm() thing which is there to avoid
races when userspace is looking at this task's name via /proc.
It obviously doesn't matter in this case, but I
Danny Kukawka napsal(a):
> On Mittwoch, 11. April 2007, Danny Kukawka wrote:
>> Jiri Slaby wrote:
>>> Corentin CHARY napsal(a):
Le Wednesday 11 April 2007 11:33:48 Jiri Slaby, vous avez écrit :
> asus_acpi, support F2JE model
Just use the new asus-laptop driver =)
(see
Correctly alter the relocation state after update is complete by switching it
from "Updating" to "Valid".
Also display the record state in the vlocation database proc file.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
fs/afs/proc.c | 15 +--
fs/afs/vlocation.c |4
On Wed, 11 Apr 2007 20:03:17 +0200
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] napisa__(a):
> > The mm snapshot broken-out-2007-04-11-02-24.tar.gz has been uploaded to
> >
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-04-11-02-24.tar.gz
> >
On Wed, 11 Apr 2007 11:00:38 -0700
Zach Brown <[EMAIL PROTECTED]> wrote:
> > - /* Compensate for the ring buffer's head/tail overlap entry */
> > - nr_events += 2; /* 1 is required, 2 for good luck */
> > + /* round nr_event to next power of 2 */
> > + nr_events =
Handle multiple mounts of an AFS superblock correctly, checking to see whether
the superblock is already initialised after calling sget() rather than just
unconditionally stamping all over it.
Also delete the "silent" parameter to afs_fill_super() as it's not used and
can, in any case, be
Permit a key to be cached in the nameidata struct so that it only needs to be
looked up once when doing the sequence of d_revalidate(), permission(),
follow_link() and lookup() calls involved in a pathwalk.
This is used by the AFS filesystem to avoid repeatedly having to call
request_key(). Once
Make two changes to the AF_RXRPC key handling to make it easier for AFS to
use:
(1) Export key_type_rxrpc so that AFS can request keys of this type.
(2) Make it possible to have keys that represent "no security". These are
created by instantiating the keys with no data.
Signed-Off-By:
Make the AF_RXRPC module use its own workqueues with their own per-CPU threads.
Currently it uses keventd to do the following tasks, amongst others:
(*) Security negotiation
(*) Packet encryption and decryption
(*) Packet resending
(*) ACK, abort and busy packet generation
(*) Timeout
These patches build on the patchset labelled "AF_RXRPC socket family and AFS
rewrite". The patches are also available for http download.
Firstly, the patches fix a number of bugs in AF_RXRPC:
http://people.redhat.com/~dhowells/rxrpc/09-af_rxrpc-own-workqueues.diff
Fix a deadlock in the give-up-callback aggregator dispatcher work item whereby
the aggregator runs on keventd as does timed autounmount, thus leading to the
unmount blocking keventd whilst waiting for keventd to run the aggregator when
the give-up-callback buffer is full.
Signed-Off-By: David
Make a couple of fixes to AF_RXRPC:
(1) The dead call timeout is shortened to 2 seconds. Without this, each
completed call sits around eating up resources for 10 seconds. The calls
need to hang around for a little while in case duplicate packets appear,
but 10 seconds is
On Apr 11 2007 20:28, Egmont Koblinger wrote:
>I send a reworked version of the patch.
>
>Removed from the first version:
> - any sign of '.' as substitute glyph
> - don't ignore zero-width characters (except for a few zero-width spaces
>that are ignored in the current kernel too).
Linux Kernel Markers documentation fix typo and use ARRAY_SIZE
Following comments from Randy Dunlap. Applies on top of the
linux-kernel-markers-documentation-markers-update-documentation patch.
Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
--- a/Documentation/marker.txt
+++
101 - 200 of 866 matches
Mail list logo
