Hi,
Kernel bug hit, while running fsstress over the CIFS mounted partition on
the ppc64 machine
cpu 0x0: Vector: 700 (Program Check) at [c00106ec75f0]
pc: c00d69cc: .kmem_cache_free+0xac/0x154
lr: c00b05f0: .mempool_free_slab+0x1c/0x30
sp: c00106ec7870
m
On Wed, 03 Oct 2007 19:41:16 -0400
Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> We also have the 64-bit inode support from RedHat/Peter Staubach.
>
As has been pointed[1] out[2], this will cause regressions for non-LFS
applications (of which there are still lots and lots). This change
should
On Thu, Oct 04, 2007 at 01:50:36AM -0400, Theodore Ts'o wrote:
> From: Mingming Cao <[EMAIL PROTECTED]>
>
> JBD: Replace slab allocations with page cache allocations
It's page allocations, not page cache allocations.
> Also this patch cleans up jbd_kmalloc and replace it with kmalloc directly
T
On Wed, Oct 03 2007, Grant Likely wrote:
> Jens,
>
> Here are some more Sysace patches based on comments received on the
> first series and a run through sparse. Can you please queue them up
> for 2.6.24?
Applied all 3, looked fine to me.
--
Jens Axboe
-
To unsubscribe from this list: send th
On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <[EMAIL PROTECTED]> wrote:
> OOPS followed by a 3 minute timeout, then completion of boot.
> Not seen if card (Kingston microSD adapter) is ejected; not seen in
> 2.6.23-rc8.
> Running on a Dell XPS M1330 laptop.
>
> `dmesg` reports:
>
> [ 13.6950
On Thu, Oct 04, 2007 at 01:59:28AM -0400, Theodore Ts'o wrote:
>
> I've just released the 2.6.23-rc9-ext4-1.
Whoops, I obviously screwed up the subject in my announcement e-mail.
Sorry about that!
- Ted
-
To unsubscribe from this list: se
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext3_next_entry() when we
I've just released the 2.6.23-rc9-ext4-1. It collapses some patches in
preparation for pushing them to Linus, and adds some of cleanup patches
that had been incorporated into Andrew's broken-out-2007-10-01-04-09
series. It also has some new development patches in the unstable (not
yet ready to p
From: Coly Li <[EMAIL PROTECTED]>
implement in future. Therefore fragment related source code in ext4 should
be obsoleted -- no one will use it.
This patch obsolete fragment from ext4. Another patch posted on linux-ext4
removing fragment supporting from e2fsprogs.
Signed-off-by: Coly Li <[EMAI
From: Jose R. Santos <[EMAIL PROTECTED]>
data is located within the storage media. This allows for the allocation
of bitmaps or inode tables outside the block group boundaries in cases
where bad blocks forces us to look for new blocks which the owning block
group can not satisfy. This will also
From: Andreas Dilger <[EMAIL PROTECTED]>
In pass1 of e2fsck, every inode table in the fileystem is scanned and checked,
regardless of whether it is in use. This is this the most time consuming part
of the filesystem check. The unintialized block group feature can greatly
reduce e2fsck time by el
From: Eric Sandeen <[EMAIL PROTECTED]>
CONFIG_EXT4_INDEX is not an exposed config option in the kernel, and it is
unconditionally defined in ext4_fs.h. tune2fs is already able to turn off
dir indexing, so at this point it's just cluttering up the code. Remove
it.
Signed-off-by: Eric Sandeen <[E
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext3
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext3 without some changes to the directory handling
code. The reason is that an empty 64kB directory block woul
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk.
Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
Signed-off-by: Mingming
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext4,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext4 without some changes to the directory handling
code. The reason is that an empty 64kB directory block wou
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext2,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext2 without some changes to the directory handling
code. The reason is that an empty 64kB directory block wou
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext4_next_entry() when we
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/fsync.c |2 +-
fs/ext4/inode.c |2 +-
fs/ext4/xattr.c |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
index 2a167d7..8d5
From: Jose R. Santos <[EMAIL PROTECTED]>
Mostly stolen from akpm's JBD cleanup patch.
- use `#ifdef foo' instead of `#if defined(foo)'
- Make journal_enable_debug __read_mostly just for the heck of it
- Make jbd_debugfs_dir and jbd_debug static
- debugfs_remove(NULL) is legal: remove unneeded
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent.ee_start to ext4_extent.ee_start_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/ext
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_r_blocks_count and s_free_blocks_count to
s_r_blocks_count_lo and s_free_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Ku
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_block_bitmap to bg_block_bitmap_lo
This helps in catching some BUGS due to direct
partial access of these split fields.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c |6 +++---
include/linux/ext4_fs.h |
The following ext4 patches are planned for submission to Linus once
the merge window for 2.6.24-rc1 is opened.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majord
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
fs/ext4/inode.c |6 --
include/linux/ext4_fs.h | 14 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_blocks_count to s_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c
From: Jan Kara <[EMAIL PROTECTED]>
We should really call journal_abort() and not __journal_abort_hard() in
case of errors. The latter call does not record the error in the journal
superblock and thus filesystem won't be marked as with errors later (and
user could happily mount it without any warn
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent_idx.ei_leaf ext4_extent_idx.ei_leaf_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/extents.c |4 ++--
includ
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_inode_bitmap and bg_inode_table to bg_inode_bitmap_lo
and bg_inode_table_lo. This helps in finding BUGs due to
direct partial access of these split 64 bit values
Also fix one direct partial access
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROT
From: Mingming Cao <[EMAIL PROTECTED]>
JBD: Replace slab allocations with page cache allocations
JBD allocate memory for committed_data and frozen_data from slab. However
JBD should not pass slab pages down to the block layer. Use page allocator
pages instead. This will also prepare JBD for the
From: Mingming Cao <[EMAIL PROTECTED]>
Convert kmalloc to kzalloc() and get rid of the memset().
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
---
fs/ext4/xattr.c |3 +--
fs/jbd2/journal.c |3 +--
fs/jbd2/transaction.c |3 +--
3 files changed, 3 insertions(+), 6 deletions
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
fs/jbd/journal.c |2 +-
fs/jbd2/journal.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/jbd/journal.c b/fs/jbd/jour
Ingo Molnar wrote:
* Jarek Poplawski <[EMAIL PROTECTED]> wrote:
[...] (Btw, in -rc8-mm2 I see new sched_slice() function which seems
to return... time.)
wrong again. That is a function, not a variable to be cleared.
It still gives us a target time, so could we not simply have sched_y
On 10/3/07, Matt Mackall <[EMAIL PROTECTED]> wrote:
> Well I can see no reason why the vma we just got to by the mm->mmap
> would have a vm_mm != mm, but I've certainly been wrong before.
>
> Try changing it to:
>
> for (vma = mm->mmap; vma; vma = vma->vm_next)
> if (!is_vm_
wmb() on x86 must always include a barrier, because stores can go out of
order in many cases when dealing with devices (eg. WC memory).
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/include/asm-i386/system.h
===
--
According to latest memory ordering specification documents from Intel and
AMD, both manufacturers are committed to in-order loads from cacheable memory
for the x86 architecture. Hence, smp_rmb() may be a simple barrier.
Also according to those documents, and according to existing practice in Lin
Hi,
Here's a couple of patches to improve the memory barrier situation on x86.
They probably aren't going upstream until after the x86 merge, however I'm
posting them here for RFC, and in case anybody wants to backport into stable
trees.
---
movnt* instructions are not strongly ordered with respe
Rob Landley wrote:
+ - The Maixm/Dallas Semiconductor DS2490 builds USB <-> W1 bridges.
Maxim (2 times)
That typo was cut and paste from the the "Description" section of both files.
(Lines 18 and 13, respectively.) :(
Attached is an updated version that spells it "maxi
On Thu, Oct 04, 2007 at 10:21:33AM +0800, Fengguang Wu wrote:
> On Wed, Oct 03, 2007 at 12:41:19PM +1000, David Chinner wrote:
> > On Wed, Oct 03, 2007 at 09:34:39AM +0800, Fengguang Wu wrote:
> > > On Wed, Oct 03, 2007 at 07:47:45AM +1000, David Chinner wrote:
> > > > On Tue, Oct 02, 2007 at 04:41
From: Arjan van de Ven <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 21:36:31 -0700
> there is still code that does DMA from and to the stack
> how would this work with virtual allocated stack?
That's a bug and must be fixed.
There honestly shouldn't be that many examples around.
FWIW, there ar
On Wed, 03 Oct 2007 20:59:49 -0700
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> Make the stack size configurable now that we can fallback to vmalloc
> if necessary. SGI NUMA configurations may need more stack because
> cpumasks and nodemasks are at times kept on the stack. With the
> coming 16k
From: Grant Likely <[EMAIL PROTECTED]>
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/block/xsysace.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/block/xsysace.c b/drivers/block/xsysace.c
index 3847464..5b73471 100644
--- a/drivers/block
Hugh Dickins wrote:
> On Wed, 3 Oct 2007, Balbir Singh wrote:
>> Hugh Dickins wrote:
>>> Sorry, Balbir, I've failed to get back to you, still attending to
>>> priorities. Let me briefly summarize my issue with the mem controller:
>>> you've not yet given enough attention to swap.
>> I am open to s
From: Grant Likely <[EMAIL PROTECTED]>
The previous patch to move the interrupt handler registration moved it
below enabling interrupts which could be a problem if the device is on
a shared interrupt line. This patch fixes the order.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/
From: Grant Likely <[EMAIL PROTECTED]>
Put function call and return code test on separate lines.
Signed-off-by: Grant Likely <[EMAIL PROTECTED]>
---
drivers/block/xsysace.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/block/xsysace.c b/drivers/block/x
The cryto subsystem needs an order 2 allocation. This is a temporary buffer
for xoring data so we can safely allow fallback.
Cc: Dan Williams <[EMAIL PROTECTED]>
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
crypto/xor.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
Jens,
Here are some more Sysace patches based on comments received on the
first series and a run through sparse. Can you please queue them up
for 2.6.24?
Thanks,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
Currently vmalloc is used for the zone wait table. Therefore the vmalloc
page tables have to be consulted by the MMU to access the wait table.
We can now use GFP_VFALLBACK to attempt the use of a physically contiguous
page that can then use the large kernel TLBs.
Drawback: The zone wait table is r
The caller table can get quite large if there are many call sites for a
particular slab. Add GFP_FALLBACK allows falling back to vmalloc in case
the caller table gets too big and memory is fragmented. Currently we
would fail the operation.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
If bit waitqueue is passed a virtual address then it must use
virt_to_head_page instead of virt_to_page.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
kernel/wait.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/kernel/wait.c
===
In an interrupt context we cannot wait for the vmlist_lock in
__get_vm_area_node(). So use a trylock instead. If the trylock fails
then the atomic allocation will fail and subsequently be retried.
This only works because the flush_cache_vunmap in use for
allocation is never performing any IPIs in
If we are in an interrupt context then simply defer the free via a workqueue.
Removing a virtual mappping *must* be done with interrupts enabled
since tlb_xx functions are called that rely on interrupts for
processor to processor communications.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]
Virtual fallbacks are rare and thus subtle bugs may creep in if we do not
test the fallbacks. CONFIG_VFALLBACK_ALWAYS makes all GFP_VFALLBACK
allocations fall back to virtual mapping.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
lib/Kconfig.debug | 11 +++
mm/page_alloc.c
Sparsemem currently attempts first to do a physically contiguous mapping
and then falls back to vmalloc. The same thing can now be accomplished
using GFP_VFALLBACK.
Cc: [EMAIL PROTECTED]
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
mm/sparse.c | 33 +++--
Peter Zijlstra has recently demonstrated that we can have order 1 allocation
failures under memory pressure with small memory configurations. The
x86_64 stack has a size of 8k and thus requires a order 1 allocation.
This patch adds a virtual fallback capability for the stack. The system may
contin
Make the stack size configurable now that we can fallback to vmalloc if
necessary. SGI NUMA configurations may need more stack because cpumasks
and nodemasks are at times kept on the stack. With the coming 16k cpu
support this is going to be 2k just for the mask. This patch allows to
run with 16k o
Make page_address() correctly determine the address of a potentially
virtually mapped compound page.
There are 3 cases to consider:
1. !HASHED_PAGE_VIRTUAL && !WANT_PAGE_VIRTUAL
Call vmalloc_address() directly from the page_address function
defined in mm.h.
2. HASHED_PAGE_VIRTUAL
Modify page_a
Add a new gfp flag
__GFP_VFALLBACK
If specified during a higher order allocation then the system will fall
back to vmap if no physically contiguous pages can be found. This will
create a virtually contiguous area instead of a physically contiguous area.
In many cases the virtually contigu
The determination of a page struct for an address in a compound page
will need some more smarts in order to deal with virtual addresses.
We need to use the evil constants VMALLOC_START and VMALLOC_END for this
and they are notoriously for referencing various arch header files or may
even be variab
Add a new function
compound_nth_page(page, n)
and
vmalloc_nth_page(page, n)
to find the nth page of a compound page. For real compound pages
his simply reduces to page + n. For virtual compound pages we need to consult
the page tables to figure out the nth page from the one speci
Make vunmap return the page array that was used at vmap. This is useful
if one has no structures to track the page array but simply stores the
virtual address somewhere. The disposition of the page array can be
decided upon after vunmap. vfree() may now also be used instead of
vunmap which will rel
Sometimes we need to figure out which vmalloc address is in use
for a certain page struct. There is no easy way to figure out
the vmalloc address from the page struct. Simply search through
the kernel page tables to find the address. Use sparingly.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTE
Add a another page flag that can be used to figure out if a compound
page is virtually mapped. The mark is necessary since we have to know
when freeing pages if we have to destroy a virtual mapping. No additional
flag is consumed through the use of PG_swapcache together with PG_compound
(similar to
Allocations of larger pages are not reliable in Linux. If larger
pages have to be allocated then one faces various choices of allowing
graceful fallback or using vmalloc with a performance penalty due
to the use of a page table. Virtual Compound pages are
a simple solution out of this dilemma. If a
The page array is repeatedly indexed both in vunmap and vmalloc_area_node().
Add a temporary variable to make it easier to read (and easier to patch
later).
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
---
mm/vmalloc.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletion
Loic Prylli <[EMAIL PROTECTED]> writes:
> Even if the INTx line is not raised, you cannot rely on the device to
> retain memory of a interrupt triggered while MSI are disabled, and
> expect it to fire it under MSI form later when MSI are reenabled.
Sure. My expectation is if we happened to hit
On Wed, 3 Oct 2007, Robert Hancock wrote:
>
> Erratum 97: 128-Bit Streaming Stores May Cause Coherency Failure
The Intel-optimized memcpy doesn't use the SSE registers, just regular
32-bit integer nontemporal stores (movnti). The reason is that the SSE
state save is too expensive to be worth
> > Why don't you use the new struct dev_archdata mechanism ? That's what I
> > use on powerpc to provide optional iommu linkage to any device in the
> > system.
> Good one. I will certainly try out your idea and will update the list
> tomorrow.
The advantage is that it allows to completely isola
Linus Torvalds wrote:
On Wed, 3 Oct 2007, Pekka Enberg wrote:
On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
I would bet that the reason the intel-optimized memcpy triggers this is
that the non-temporal stores just means that you go out directly on the
bus, and it probably just shows a
One more cgroup code review detail ...
The following is evidence of some more stale comments in
kernel/cpuset.c. Some routines which used to be in that file, but
which are now reimplemented in cgroups, are still named in cpuset.c
comments:
$ grep -E 'cpuset_rmdir|cpuset_exit|cpuset_fork' kernel/
On 10/3/07, Paul Jackson <[EMAIL PROTECTED]> wrote:
>
> I can't say for sure, but I suspect that if cgroups had always
> been cgroups (short for control groups), then these local 'cont'
> variables would have a different name.
Oh, absolutely. I just refrained from changing them in the rename
since
> > - There are many instances of the local variable 'cont', referring
> >to a struct cgroup pointer. I presume the spelling 'cont' is a
> >holdover from the time when we called these containers.
>
> Yes, and since cgroup is short for "control group", "cont" still
> seemed like a reasona
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exec
Fix a horribly mangled 5 level indent and severe abuse of goto in the
open_exec
function.
Signed-off-
On Wed, Oct 03, 2007 at 12:41:19PM +1000, David Chinner wrote:
> On Wed, Oct 03, 2007 at 09:34:39AM +0800, Fengguang Wu wrote:
> > On Wed, Oct 03, 2007 at 07:47:45AM +1000, David Chinner wrote:
> > > On Tue, Oct 02, 2007 at 04:41:48PM +0800, Fengguang Wu wrote:
> > > > wbc.pages_ski
Hernan G Solari wrote:
>>> netconsole, pritty nice debunging system... but (yes, there is always
>>> a but) it does not get to run.
>>> the method was well implemented, adding the acpi=off it sends the
>>> information to the receiving machine (I can even see passing a
>>> netconsole probing mes
Jimmy wrote:
I know I'll be getting hell for this, I must be a masochist.
Anyway, I've been trying to figure out what purpose the gpl-only code
serves.
What good comes out of disabling people from probing modules that do not
have a gpl-compatible license?
Who is disabling anything?
Of cause
> On Wed, 3 Oct 2007, Yasunori Goto wrote:
>
> > >
> > > That would work. But it would be better to shrink the cache first. The
> > > first 2 slabs on a node may be empty and the shrinking will remove those.
> > > If you do not shrink then the code may falsely assume that there are
> > > objec
On Wed, Oct 03, 2007 at 01:46:52PM +0100, richard kennedy wrote:
> On Tue, 2007-10-02 at 10:00 +0800, Fengguang Wu wrote:
> > ---
> > mm/page-writeback.c |5 +
> > 1 file changed, 5 insertions(+)
> >
> > --- linux-2.6.22.orig/mm/page-writeback.c
> > +++ linux-2.6.22/mm/page-writeback.c
>
On Wednesday 03 October 2007 4:38:49 pm Randy Dunlap wrote:
> On Wed, 03 Oct 2007 14:17:33 -0700 [EMAIL PROTECTED] wrote:
> > The patch titled
> > Add Documentation/{w1,w1/masters}/00-INDEX
> > has been added to the -mm tree. Its filename is
> > add-documentation-w1w1-masters-00-index.pa
Hi,
From: Linus Torvalds <[EMAIL PROTECTED]>
> On Wed, 3 Oct 2007, Pekka Enberg wrote:
> >
> > On 10/3/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> > > I would bet that the reason the intel-optimized memcpy triggers this is
> > > that the non-temporal stores just means that you go out directly
On 10/3/2007 5:49 PM, Eric W. Biederman wrote:
> Loic Prylli <[EMAIL PROTECTED]> writes:
>
>
>> Hi,
>>
>> We observe a problem with MSI since kernel 2.6.21 where interrupts would
>> randomly stop working. We have tracked it down to the new
>> msi_set_mask_bit definition in 2.6.21. In the MSI cas
On Thu, Oct 04, 2007 at 11:19:33AM +1000, Benjamin Herrenschmidt wrote:
> > Index: 2.6-mm/include/linux/pci.h
> > ===
> > --- 2.6-mm.orig/include/linux/pci.h 2007-10-03 13:48:20.0 -0700
> > +++ 2.6-mm/include/linux/pci.h 2
> Index: 2.6-mm/include/linux/pci.h
> ===
> --- 2.6-mm.orig/include/linux/pci.h 2007-10-03 13:48:20.0 -0700
> +++ 2.6-mm/include/linux/pci.h2007-10-03 13:49:08.0 -0700
> @@ -195,6 +195,7 @@
> #ifdef CONFIG_PC
--- Al Viro <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 03, 2007 at 03:23:15PM -0700, Casey Schaufler wrote:
> > 1. Create /moldy at "_"
> > 2. For each label you care about
> >2a. Create /moldy/
> >2b. Set the label of /moldy/ to
> > 3. ln -s /smack/tmp /tmp
>
> > 1. Create /moldy at "_"
On Mon, 2007-10-01 at 09:49 -0700, David Schwartz wrote:
> > * Jarek Poplawski <[EMAIL PROTECTED]> wrote:
> >
> > > BTW, it looks like risky to criticise sched_yield too much: some
> > > people can misinterpret such discussions and stop using this at all,
> > > even where it's right.
>
> > Really,
Rusty Russell wrote:
On Wed, 2007-10-03 at 10:37 +0100, Chris Malley wrote:
Hi guys
Would it not be clearer to #include and use
the relevant named members of struct setup_header / struct boot_params
rather than the hard-coded values 0x202, 0x1F1, 0x214 ?
Yes, but unfortunately bootparam.h
On Wed, 2007-10-03 at 10:37 +0100, Chris Malley wrote:
> Hi guys
>
> Would it not be clearer to #include and use
> the relevant named members of struct setup_header / struct boot_params
> rather than the hard-coded values 0x202, 0x1F1, 0x214 ?
Yes, but unfortunately bootparam.h wasn't designed
Trond Myklebust wrote:
Aside from the usual updates from Chuck for NFS-over-IPv6 (still
incomplete) and a number of bugfixes for the text-based mount code, the
main news in the NFS tree is the merging of support for the NFS/RDMA
client code from Tom Talpey and the NetApp New England (NANE) team.
On 7/17/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
>
> > Ingo Molnar wrote:
> > > Subject: softlockup: fix Xen bogosity
> > > From: Ingo Molnar <[EMAIL PROTECTED]>
> > >
> > > this Xen related commit:
> > >
> >
> > Well, not just Xen. It relates
On Wed, 3 Oct 2007 17:32:55 -0600
"Patro, Sumant" <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: FUJITA Tomonori [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 02, 2007 5:01 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> > linux-ker
Aside from the usual updates from Chuck for NFS-over-IPv6 (still
incomplete) and a number of bugfixes for the text-based mount code, the
main news in the NFS tree is the merging of support for the NFS/RDMA
client code from Tom Talpey and the NetApp New England (NANE) team.
We also have the 64-bit
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 15:05:19 -0700
> On Wed, 03 Oct 2007 14:58:07 -0700 (PDT)
> David Miller <[EMAIL PROTECTED]> wrote:
>
> > From: Peter Zijlstra <[EMAIL PROTECTED]>
> > Date: Wed, 03 Oct 2007 17:44:53 +0200
> >
> > > Index: linux-2.6/net/core/dev.c
> -Original Message-
> From: FUJITA Tomonori [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 02, 2007 5:01 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> linux-kernel@vger.kernel.org; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; Patro, Sumant; DL-MegaRAID
> Li
On Wednesday 03 October 2007, you wrote:
> On Wed, Oct 03, 2007 at 09:27:41PM +0200, Frans Pop wrote:
> > On Wednesday 03 October 2007, you wrote:
> > > On Wed, 3 Oct 2007, Ilpo Järvinen wrote:
> > > > On Wed, 3 Oct 2007, Frans Pop wrote:
> > > > > The only change is in 2 consecutive columns: "2911
On Wed, 3 Oct 2007, Serge E. Hallyn wrote:
>
> Signed-off-by: Serge Hallyn <[EMAIL PROTECTED]>
Acked-by: James Morris <[EMAIL PROTECTED]>
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Wed, Oct 03, 2007 at 03:23:15PM -0700, Casey Schaufler wrote:
> 1. Create /moldy at "_"
> 2. For each label you care about
>2a. Create /moldy/
>2b. Set the label of /moldy/ to
> 3. ln -s /smack/tmp /tmp
> 1. Create /moldy at "_"
> 2. For each label you care about
>2a. Create /moldy
On Wednesday 03 October 2007, Arnd Bergmann wrote:
> Jens, I think the best overall solution would be to have a
> block/compat_ioctl.c file with all the compat handling for block
> devices moved over from fs/compat_ioctl.c, and done in a nicer way.
> If you agree, with this approach, I'd volunteer
On Wed, 3 Oct 2007, Serge E. Hallyn wrote:
> >From 54c70ca7671750fe8986451fae91d42107d0ca90 Mon Sep 17 00:00:00 2001
> From: Serge E. Hallyn <[EMAIL PROTECTED]>
> Date: Fri, 28 Sep 2007 10:33:33 -0500
> Subject: [PATCH 1/2 -mm] capabilities: define CONFIG_COMMONCAP
>
> currently the compilation o
On Wed, 03 Oct 2007 14:17:33 -0700 [EMAIL PROTECTED] wrote:
>
> The patch titled
> Add Documentation/{w1,w1/masters}/00-INDEX
> has been added to the -mm tree. Its filename is
> add-documentation-w1w1-masters-00-index.patch
>
> *** Remember to use Documentation/SubmitChecklist when te
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed, 3 Oct 2007 14:39:16 -0400
>
> Normally I wait a day or two between pushes, to queue up patches and
> also to avoid annoying my upstream :) But this includes a couple fixes
> I felt should be upstreamed sooner rather than later.
>
> Please pull fr
>From d93ecb90d82f9e2b7f48c74f5e6ed97cac3683c7 Mon Sep 17 00:00:00 2001
From: Serge Hallyn <[EMAIL PROTECTED]>
Date: Fri, 28 Sep 2007 10:33:56 -0500
Subject: [PATCH 2/2 -mm] capabilities: introduce per-process capability
bounding set (v4)
The capability bounding set is a set beyond which capabili
1 - 100 of 380 matches
Mail list logo
