Rik van Riel a écrit :
Eric Dumazet wrote:
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
Bartek wrote:
> Hopefully, this time it my bug report should be ok :):
>
> Apr 11 23:53:38 localhost pppd[31289]: rcvd [proto=0x7689] e1 cd 33 f6
> fd f7 52 e6 58 c9 73 98 bc ff ad d5 b5 a3 e5 d9 1e 77 76 0a 1c 87 59
> bf 44 cc ac 3b ...
> Apr 11 23:53:38 localhost pppd[31289]: Unsupported
On Thursday 12 April 2007 02:04, Al Boldi wrote:
> > Pedro wrote:
> > 2) How should an application be written to not be killed by OOM?
>
> Try this:
>
> # echo -17 > /proc//oom_adj
I should know that to run a fail-safe application is a superuser privilege.
Sorry from wasting your time.
-
Add comment and condense code to make use of native_local_ptep_get_and_clear
function. Also, it turns out the 2-level and 3-level paging definitions
were identical, so move the common definition into pgtable.h
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r b3bbc1b5e085
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the heavyweight
xchg instruction to atomically fetch and clear page table entries. Instead,
we can just read and clear them directly.
This introduces a neat
In shadow mode hypervisors, ptep_get_and_clear achieves the desired
purpose of keeping the shadows in sync by issuing a native_get_and_clear,
followed by a call to pte_update, which indicates the PTE has been
modified.
Direct mode hypervisors (Xen) have no need for this anyway, and will trap
the
When exiting from an address space, no special hypervisor notification of page
table updates needs to occur; direct page table hypervisors, such as Xen,
switch to another address space first (init_mm) and unprotects the page tables
to avoid the cost of trapping to the hypervisor for each
Some PTE optimizations for native and paravirt-ops kernels; this
provides a huge win for shadow mode hypervisors and gets rid of
some unnecessary atomic instructions in native kernels, saving
even more on UP by getting rid of implicit LOCK on xchg instruction.
Zach
-
To unsubscribe from this
On Wed, 2007-04-11 at 19:03 +0200, Patrick McHardy wrote:
>
> You bring up a good point, it would be good to hear the opinion from
> one of the wireless people on this since they have their own
> multiqueue scheduler in the wireless-dev tree.
The one in the wireless-dev is pretty much like this
On Wednesday 11 April 2007 19:39, Alan Cox wrote:
> > 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
It is not enough to unload proprietary modules. As long as they have
ever been loaded at all the kernel is tainted.
You need to ensure that the proprietary modules never get loaded at
all. I guess you probably already worked that out, just wanted to
point it out just in case :-)
Hopefully, this
Pedro wrote:
> On Wednesday 11 April 2007 16:48, Willy Tarreau wrote:
> > On Wed, Apr 11, 2007 at 02:23:31AM -0300, Pedro wrote:
> > >
> > > As the OOM killer is not Posix,
> >
> > If you cannot control your application's memory usage, you'll have to
> > finely tune the overcommit_ratio.
>
>
ROUND_UP macro cleanup, use ALIGN where ever appropriate.
Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
---
pci_sh5.c | 12
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/arch/sh64/kernel/pci_sh5.c b/arch/sh64/kernel/pci_sh5.c
index 9dae689..11d1fef
On 4/10/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
On Tue, 10 Apr 2007, Jeff Chua wrote:
> I couldn't get suspend-to-disk to work with 2.6.21-rc6. I've tried
> set/unset CONFIG_NO_HZ/CONFIG_HPET_TIMER, but nothing worked.
Do you think you could busect it? You'd have to apply maxim's patch by
On Thu, Apr 12, 2007 at 03:25:03AM +0400, Anton Vorontsov wrote:
> Here is battery monitor class. According to first copyright string, we're
> maintaining it since 2003. I've took few days and cleaned it up to be
> more suitable for mainline inclusion.
>
> It differs from battery class at
On Thu, 12 Apr 2007 03:25:03 +0400 Anton Vorontsov wrote:
> Here is battery monitor class. According to first copyright string, we're
> maintaining it since 2003. I've took few days and cleaned it up to be
> more suitable for mainline inclusion.
>
> ---
> drivers/Kconfig |2 +
>
> Is there any support consideration for nommu arch such as blackfin which
> is in the -mm tree now?
>
> It is very kind of you to point out some idea about MAP_FIXED for
> Blackfin arch, I will do some help for this.
Right now, my understanding is that nommu archs just reject MAP_FIXED
Now that read_mapping_page() does error checking internally, there is no
need to check PageError here.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc6-mm1/fs/hfs/bnode.c
linux-2.6.21-rc6-mm1-test/fs/hfs/bnode.c
--- linux-2.6.21-rc6-mm1/fs/hfs/bnode.c
Replace jffs2_gc_fetch_page() and jffs2_gc_release_page() using the
read_cache_page() and put_kmapped_page() calls, and update the call site
accordingly. Explicit calls to kmap()/kunmap() make the code more clear.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff
Replace ntfs_map_page() and ntfs_unmap_page() using the new read_kmap_page()
and put_kmapped_page() calls, and their locking variants, and remove
unneeded PageError checking.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc5-mm4/fs/ntfs/aops.h
read_mapping_page_async() is going away, so convert its only user to
read_mapping_page(). This change has not been benchmarked, however, in
order to get real parallelism this wants something completely different,
like __do_page_cache_readahead(), which is not currently exported.
Signed-off-by:
Now that read_mapping_page() does error checking internally, there is no
need to check PageError here.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc6-mm1/fs/hfsplus/bnode.c
linux-2.6.21-rc6-mm1-test/fs/hfsplus/bnode.c
---
Replace reiserfs_get_page() and reiserfs_put_page() using the new
read_kmap_page() and put_kmapped_page() calls and their locking variants.
Also, propagate the gfp_mask() deadlock comment to callsites.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff
Replace vxfs_get_page() with the new read_kmap_page().
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc5-mm4/fs/freevxfs/vxfs_extern.h
linux-2.6.21-rc5-mm4-test/fs/freevxfs/vxfs_extern.h
--- linux-2.6.21-rc5-mm4/fs/freevxfs/vxfs_extern.h 2007-04-05
Replace sysv dir_get_page() with the new read_kmap_page().
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc5-mm4/fs/sysv/dir.c
linux-2.6.21-rc5-mm4-test/fs/sysv/dir.c
--- linux-2.6.21-rc5-mm4/fs/sysv/dir.c 2007-04-05 17:14:25.0 -0700
+++
On Thu, 2007-04-12 at 12:20 +1000, Benjamin Herrenschmidt wrote:
> This is a "first step" as there are still cleanups to be done in various
> areas touched by that code but I think it's probably good to go as is and
> at least enables me to implement what I need for PowerPC.
>
> (Andrew, this is
Replace ufs_get_page()/ufs_get_locked_page() and
ufs_put_page()/ufs_put_locked_page() using the new read_kmap_page() and
put_kmapped_page() calls and their locking variants. Also, change the
ufs_check_page() call to return the page's error status, and update the
call sites accordingly.
read_mapping_page() is now fully synchronous, so there's no need wait for
the page lock or check for I/O errors.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff
linux-2.6.21-rc6-mm1/fs/reiser4/plugin/file/tail_conversion.c
Remove unneeded PageError checking in read_dev_sector(), and clean up the
code a bit.
Can anyone point out why it's OK to use page_address() here on a page which
has not been kmapped? If it's not OK, then a good number of callers need to
be fixed.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
Replace minix dir_get_page() and dir_put_page() using the new
read_kmap_page() and put_kmapped_page()/put_locked_page() calls. Also, use
__read_kmap_page() instead of re-taking the page_lock.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff
Replace page_read() with read_kmap_page()/__read_kmap_page(). This probably
fixes behaviour on highmem systems, since page_address() was being used
without kmap(). Also eliminate the need to re-take the page lock during
writes to the page.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
Replace ext2_get_page() and ext2_put_page() using the new read_kmap_page()
and put_kmapped_page() calls. Also, change the ext2_check_page() call to
return the page's error status, and update the call sites accordingly.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff
Use the new locking variant of read_mapping_page to avoid doing extra work.
Signed-off-by: Nate Diller <[EMAIL PROTECTED]>
---
diff -urpN -X dontdiff linux-2.6.21-rc6-mm1/fs/jfs/jfs_metapage.c
linux-2.6.21-rc6-mm1-test/fs/jfs/jfs_metapage.c
--- linux-2.6.21-rc6-mm1/fs/jfs/jfs_metapage.c
Export a single version of read_cache_page, which returns with a locked,
Uptodate page or a synchronous error, and use inline helper functions to
replicate the old behavior. Also, introduce new helper functions for the
most common file system uses, which include kmapping the page, as well as
Replace afs_dir_get_page() and afs_dir_put_page() using the new
read_kmap_page() and put_kmapped_page() calls, and eliminate unnecessary
PageError checks. Also, change the afs_dir_check_page() call to return
the page's error status, and update the call site accordingly.
Signed-off-by: Nate
Nick Piggin recently changed the read_cache_page interface to be
synchronous, which is pretty much what the file systems want anyway. Turns
out that they have more in common than that, though, and some of them want
to be able to get an uptodate *locked* page. Many of them want a kmapped
page,
On Thu, 12 April 2007 11:46:41 +1000, Neil Brown wrote:
>
> I could argue that nfs came before ext3+dirindex, so ext3 should have
> been designed to work properly with NFS. You could argue that fixing
> it in nfsd fixes it for all filesystems. But I'm not sure either of
> those arguments are
The Linux-ready Firmware Developer Kit team is pleased to announce the
release R2 of the kit.
This release is mostly very heavy with bug-fixes,
infrastructure re-org. to make it easier for outside developers to
write & contribute plugins, and of course, tons of documentation. A few
new tests
Handle MAP_FIXED in parisc arch_get_unmapped_area(), just return the
address. We might want to also check for possible cache aliasing
issues now that we get called in that case (like ARM or MIPS),
leave a comment for the maintainers to pick up.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL
Handle MAP_FIXED in ia64 arch_get_unmapped_area and
hugetlb_get_unmapped_area(), just call prepare_hugepage_range
in the later and is_hugepage_only_range() in the former.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/ia64/kernel/sys_ia64.c |7 +++
Handle MAP_FIXED in i386 hugetlb_get_unmapped_area(), just call
prepare_hugepage_range.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/i386/mm/hugetlbpage.c |6 ++
1 file changed, 6 insertions(+)
Index: linux-cell/arch/i386/mm/hugetlbpage.c
Handle MAP_FIXED in arch_get_unmapped_area on frv. Trivial case, just
return the address.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/frv/mm/elf-fdpic.c |4
1 file changed, 4 insertions(+)
Index: linux-cell/arch/frv/mm/elf-fdpic.c
Handle MAP_FIXED in x86_64 arch_get_unmapped_area(), simple case, just
return the address as passed in
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/x86_64/kernel/sys_x86_64.c |3 +++
1 file changed, 3 insertions(+)
Index: linux-cell/arch/x86_64/kernel/sys_x86_64.c
Handle MAP_FIXED in hugetlb_get_unmapped_area on sparc64
by just using prepare_hugepage_range()
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/sparc64/mm/hugetlbpage.c |6 ++
1 file changed, 6 insertions(+)
Index: linux-cell/arch/sparc64/mm/hugetlbpage.c
Remove the hugetlbfs specific hacks in toplevel get_unmapped_area() now
that all archs and hugetlbfs itself do the right thing for both cases.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
mm/mmap.c | 16
1 file changed, 16 deletions(-)
Index:
Generic hugetlb_get_unmapped_area() now handles MAP_FIXED by just
calling prepare_hugepage_range()
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
fs/hugetlbfs/inode.c |6 ++
1 file changed, 6 insertions(+)
Index: linux-cell/fs/hugetlbfs/inode.c
generic arch_get_unmapped_area() now handles MAP_FIXED. Now that
all implementations have been fixed, change the toplevel
get_unmapped_area() to call into arch or drivers for the MAP_FIXED
case.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
mm/mmap.c | 25 +++--
Handle MAP_FIXED in alpha's arch_get_unmapped_area(), simple case, just
return the address as passed in
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/alpha/kernel/osf_sys.c |3 +++
1 file changed, 3 insertions(+)
Index: linux-cell/arch/alpha/kernel/osf_sys.c
ARM already had a case for MAP_FIXED in arch_get_unmapped_area() though
it was not called before. Fix the comment to reflect that it will now
be called.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/arm/mm/mmap.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Handle MAP_FIXED in powerpc's arch_get_unmapped_area() in all 3
implementations of it.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
arch/powerpc/mm/hugetlbpage.c | 21 +
1 file changed, 21 insertions(+)
Index: linux-cell/arch/powerpc/mm/hugetlbpage.c
This is a "first step" as there are still cleanups to be done in various
areas touched by that code but I think it's probably good to go as is and
at least enables me to implement what I need for PowerPC.
(Andrew, this is also candidate for 2.6.22 since I haven't had any real
objection, mostly
On Tue, Apr 03, 2007 at 10:48:20PM +0530, Srivatsa Vaddagiri wrote:
> > Actually, we should do this before destroy_workqueue() calls
> > flush_workqueue().
> > Otherwise flush_cpu_workqueue() can hang forever in a similar manner.
>
> Yep. I guess these are a class of freezer deadlocks very
The latest maintenance release GIT 1.5.1.1 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.5.1.1.tar.{gz,bz2} (tarball)
git-htmldocs-1.5.1.1.tar.{gz,bz2} (preformatted docs)
git-manpages-1.5.1.1.tar.{gz,bz2}
Eric Dumazet wrote:
On Wed, 11 Apr 2007 19:23:26 +1000
Nick Piggin <[EMAIL PROTECTED]> wrote:
As this external thing certainly is not doing the check itself, to be on the
safe side we should enforce it in get_futex_key(). I agree with you : If we
want to maximize performance, we could say :
On Wednesday April 11, [EMAIL PROTECTED] wrote:
>
> Actually, no, we can't keep the collision chain count stable across a
> create/delete even while the tree is cached. At least, not without
> storing a huge amount of state associated with each page. (It would
> be a lot more work than simply
While digging through my MAP_FIXED changes, I found that rather obvious
bug in /dev/mem mmap implementation for nommu archs. get_unmapped_area()
is expected to return an address, not a pfn.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
---
I suppose that can go in anytime, and
Chris Wright wrote:
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
+void __init vmi_time_init(void)
+{
+ /* Disable PIT: BIOSes start PIT CH0 with 18.2hz peridic. */
+ outb_p(0x3a, PIT_MODE); /* binary, mode 5, LSB/MSB, ch 0 */
That shouldn't be necessary using
Carlo Florendo wrote:
IIRC, The kernel does some encryption functions, involving TCP, NFS, and
IPsec since all these are part of the kernel itself.
Yes, but key management is done in userspace.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
JanuGerman 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 seperately in this regard.
Robert P. J. Day wrote:
(in short, if i, the builder, explicitly choose *not* to add a
certain feature to my build, i think i have every right to expect that
some other part of my configuration isn't quietly going to put some
sub-choice of that feature back in behind my back.)
I agree with
> diff --git a/drivers/Kconfig b/drivers/Kconfig
> index 050323f..c546de3 100644
I've forgot to pass -s flag to git-format-patch. :-/
Please count it for whole x/7 patch set:
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe
>From: Randy Dunlap <[EMAIL PROTECTED]>
>
>Make kernel-doc comments match macro names.
>Correct parameter names in a few places.
>Remove '#' from beginning of kernel-doc comment macro names.
>Remove extra (erroneous) blank lines in kernel-doc.
>
> ...
>
>cc: Inaky Perez-Gonzalez <[EMAIL
On Wed, 11 Apr 2007 14:33:57 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> > Here is the call ordering ,
> >
> > ktime_get()
> > ktime_get_ts() -> read_seqretry(_lock, seq)
> > getnstimeofday()
> >__get_realtime_clock_ts() -> read_seqretry(_lock, seq)
> >
> >
> > I wonder if there is
From: Randy Dunlap <[EMAIL PROTECTED]>
Make kernel-doc comments match macro names.
Correct parameter names in a few places.
Remove '#' from beginning of kernel-doc comment macro names.
Remove extra (erroneous) blank lines in kernel-doc.
Warning(plist.h:100): Cannot understand * #PLIST_HEAD_INIT
> 1) When physical memory runs low, the memory manager will try to use
> memory currently allocated to the pagecache. Is this true?
Yes.
> 2) When vm.overcommit_memory = 2 (overcommit disabled), and memory runs
> low, it appears that the memory manager does not try to use memory
> currently
Jim Keniston wrote:
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
Hi, Peter:
There's one thing I wanted to report, just in case... It does not affect
anything, but it's odd.
Every time I lift a finger from the pad, the driver sends an event with
odd values (X is 1 and Y is 5855):
Event: time 1174695694.561806, type 1 (Key), code 330 (Touch), value 0
Event:
On Wednesday April 11, [EMAIL PROTECTED] wrote:
> 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
It finds battery with "main_battery" flag set (or with max_capacity if no
batteries marked as main), and converts battery values to APM form.
---
drivers/battery/Kconfig |7 +++
drivers/battery/Makefile|1 +
drivers/battery/apm_power.c | 121
This is driver for batteries with ds2760 chip inside. Such batteries
used in almost every HP iPaq and HTC PDAs/phones.
---
drivers/battery/Kconfig |7 +
drivers/battery/Makefile |1 +
drivers/battery/ds2760_battery.c | 466 ++
Trivial patch, against -rc6. Please apply, thanks.
---
CREDITS:
- Summarize 3 lines into one.
- Add webpage.
MAINTAINERS:
- Add auxdisplay drivers/tree webpages.
CREDITS |7 +++
MAINTAINERS |4
2 files changed, 7 insertions(+), 4 deletions(-)
Signed-off-by: Miguel Ojeda
On Wed, 11 April 2007 16:23:21 -0700, H. Peter Anvin wrote:
> David Lang wrote:
> >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
> >>
This is W1 slave for ds2760 chip, found inside almost every HP iPaq and
HTC PDAs/phones.
---
drivers/w1/slaves/Kconfig | 13 +++
drivers/w1/slaves/Makefile|1 +
drivers/w1/slaves/w1_ds2760.c | 162 +
drivers/w1/slaves/w1_ds2760.h | 52
On Mon, Apr 09, 2007 at 04:13:28PM -0700, Siddha, Suresh B wrote:
> On Mon, Apr 09, 2007 at 03:05:01PM -0700, [EMAIL PROTECTED] wrote:
> > Subject: x86_64-set-node_possible_map-at-runtime fix
> > From: David Rientjes <[EMAIL PROTECTED]>
> >
> > Clear node_possible_map if numa_emulation() fails
This function were placed in "#if 0" because nobody was using it. We do use.
See http://lwn.net/Articles/210610/
---
drivers/base/bus.c |5 ++---
include/linux/device.h |2 ++
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/base/bus.c b/drivers/base/bus.c
Here is battery monitor class. According to first copyright string, we're
maintaining it since 2003. I've took few days and cleaned it up to be
more suitable for mainline inclusion.
It differs from battery class at git://git.infradead.org/battery-2.6.git:
* It's using external power kernel
External power framework - power supplies and power supplicants.
Supplicants (batteries so far) may ask to notify they when power supply
arrive/gone. This framework used by battery class (next patches).
It's permitted for supply to be bound to several supplicants (think main
and backup
This driver used to stop code/logic duplication through different
machines we porting at handhelds.org. pda_power register machs' power
supplies, and will take care about notifying batteries about power
changes through external power interface.
This driver should be suitable for almost every
David Lang wrote:
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
On Thu, 12 Apr 2007 01:07:00 +0200
Helge Hafting <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 11, 2007 at 01:43:46PM -0700, Andrew Morton wrote:
> >
> > OK. If you add initcall_debug to the kernel boot command line, what's the
> > last thing we call?
>
> The last messages (handwritten, somewhat
On Thu, Apr 12, 2007 at 08:32:05AM +1000, Neil Brown wrote:
> For the first:
> You are storing an internal tree representation of part of the
> directory attached to the 'struct file'.
> Would it be possible to store this attached to the page via the
> ->private pointer? What would avoid
-stable review patch. If anyone has any objections, please let us know.
--
From: Adam Kropelin <[EMAIL PROTECTED]>
HID: Do not discard truncated input reports
Truncated reports should not be discarded since it prevents buggy
devices from communicating with userspace.
Prior to
On Wed, Apr 11, 2007 at 01:43:46PM -0700, Andrew Morton wrote:
>
> OK. If you add initcall_debug to the kernel boot command line, what's the
> last thing we call?
The last messages (handwritten, somewhat shortened)
calling hid_init+0x0/0x10()
returned 0
ran for 0 msec
calling
-stable review patch. If anyone has any objections, please let us know.
--
From: Neil Brown <[EMAIL PROTECTED]>
If 'num_pages' were ever 1 more than a multiple of 8 (32bit platforms)
for of 16 (64 bit platforms). filemap_attr would be allocated one
'unsigned long' shorter than
-stable review patch. If anyone has any objections, please let us know.
--
From: Andreas Oberritter <[EMAIL PROTECTED]>
DVB: pluto2: fix incorrect TSCR register setting
The ADEF bits in the TSCR register have different meanings in read
and write mode. For this reason ADEF has
-stable review patch. If anyone has any objections, please let us know.
--
From: Stephen Hemminger <[EMAIL PROTECTED]>
The workaround Yukon EC-U wasn't comparing with correct
version and wasn't doing correct setup. Without it, 88e8056
throws all sorts of errors.
Signed-off-by:
-stable review patch. If anyone has any objections, please let us know.
--
From: Patrick McHardy <[EMAIL PROTECTED]>
[IFB]: Fix crash on input device removal
The input_device pointer is not refcounted, which means the device may
disappear while packets are queued, causing a
-stable review patch. If anyone has any objections, please let us know.
--
From: Francois Romieu <[EMAIL PROTECTED]>
Your usual dont-flush_scheduled_work-with-RTNL-held stuff.
It is a bit different here since the thread runs permanently
or is only occasionally kicked for
-stable review patch. If anyone has any objections, please let us know.
--
From: Stephen Hemminger <[EMAIL PROTECTED]>
Some of these chips are disabled until clock is enabled.
This fixes:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404107
Signed-off-by: Stephen
-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.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
-stable review patch. If anyone has any objections, please let us know.
--
From: David Miller <[EMAIL PROTECTED]>
[TCP]: slow_start_after_idle should influence cwnd validation too
For the cases that slow_start_after_idle are meant to deal
with, it is almost a certainty that the
-stable review patch. If anyone has any objections, please let us know.
--
From: Neil Brown <[EMAIL PROTECTED]>
[PATCH] knfsd: allow nfsd READDIR to return 64bit cookies
->readdir passes lofft_t offsets (used as nfs cookies) to
nfs3svc_encode_entry{,_plus}, but when they pass
-stable review patch. If anyone has any objections, please let us know.
--
From: Herbert Xu <[EMAIL PROTECTED]>
[IPSEC]: Reject packets within replay window but outside the bit mask
Up until this point we've accepted replay window settings greater than
32 but our bit mask can
-stable review patch. If anyone has any objections, please let us know.
--
From: Suleiman Souhlal <[EMAIL PROTECTED]>
ide: use correct IDE error recovery
IDE error recovery is using IDLE IMMEDIATE if the drive is busy or has DRQ set.
This violates the ATA spec (can only send
-stable review patch. If anyone has any objections, please let us know.
--
From: Patrick McHardy <[EMAIL PROTECTED]>
[NET_SCHED]: cls_tcindex: fix compatibility breakage
Userspace uses an integer for TCA_TCINDEX_SHIFT, the kernel was changed
to expect and use a u16 value in
-stable review patch. If anyone has any objections, please let us know.
--
From: Brian Pomerantz <[EMAIL PROTECTED]>
When the dump cannot occur most likely because of a full file system and
the page to be written is the zero page, the call to page_cache_release()
is missed.
Eric Dumazet wrote:
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
Hi.
On Sun, 2007-04-01 at 23:17 +0200, Sam Ravnborg wrote:
> On Thu, Feb 01, 2007 at 02:05:49PM +1100, Nigel Cunningham wrote:
> > Hi.
> >
> > The scripts/kconfig/mconf target isn't removed by the make mrproper
> > target. I can see a couple of possibilities, but wasn't sure which you'd
> >
Andrew Morton <[EMAIL PROTECTED]> writes:
> [...] I am told that the systemtap developers plan to (or are)
> using this infrastructure.
Indeed.
> If correct: what is their reason for preferring it over kprobes?
> [...]
It's not a preference - it's more of a supplement. It's helpful when
-stable review patch. If anyone has any objections, please let us know.
--
From: John Heffner <[EMAIL PROTECTED]>
[TCP]: Do receiver-side SWS avoidance for rcvbuf < MSS.
Signed-off-by: John Heffner <[EMAIL PROTECTED]>
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
1 - 100 of 866 matches
Mail list logo
