On Thu, 2007-12-13 at 00:42 +0100, Andi Kleen wrote:
> > I appear to have misread d_find_alias(). It would seem that the only way
> > to ensure that a mountpoint won't be found is to remove it altogether
> > from the inode->i_dentry list. AFAICS that should be largely harmless
> > since the nfs
> I appear to have misread d_find_alias(). It would seem that the only way
> to ensure that a mountpoint won't be found is to remove it altogether
> from the inode->i_dentry list. AFAICS that should be largely harmless
> since the nfs sb->s_root is never visible to users, and is never part of
> a
I appear to have misread d_find_alias(). It would seem that the only way
to ensure that a mountpoint won't be found is to remove it altogether
from the inode-i_dentry list. AFAICS that should be largely harmless
since the nfs sb-s_root is never visible to users, and is never part of
a dentry
On Thu, 2007-12-13 at 00:42 +0100, Andi Kleen wrote:
I appear to have misread d_find_alias(). It would seem that the only way
to ensure that a mountpoint won't be found is to remove it altogether
from the inode-i_dentry list. AFAICS that should be largely harmless
since the nfs sb-s_root
On Mon, 2007-12-10 at 19:57 +0100, Andi Kleen wrote:
> > Hi Andi,
> >
> > Does the attached patch fix the Oops?
>
> Nope, got that a few hours after boot again:
>
> -Andi
Hi Andi,
I appear to have misread d_find_alias(). It would seem that the only way
to ensure that a mountpoint won't be
On Mon, 2007-12-10 at 19:57 +0100, Andi Kleen wrote:
Hi Andi,
Does the attached patch fix the Oops?
Nope, got that a few hours after boot again:
-Andi
Hi Andi,
I appear to have misread d_find_alias(). It would seem that the only way
to ensure that a mountpoint won't be found is to
> Hi Andi,
>
> Does the attached patch fix the Oops?
Nope, got that a few hours after boot again:
-Andi
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[ cut here ]
kernel BUG at fs/dcache.c:595!
invalid opcode: [1] SMP
CPU 0
Hi Andi,
Does the attached patch fix the Oops?
Nope, got that a few hours after boot again:
-Andi
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[ cut here ]
kernel BUG at fs/dcache.c:595!
invalid opcode: [1] SMP
CPU 0
On Sat, 2007-12-08 at 14:22 +0100, Andi Kleen wrote:
> [39943.212533] [ cut here ]
> [39943.221973] kernel BUG at fs/dcache.c:595!
> [39943.230369] invalid opcode: [1] SMP
> [39943.238638] last sysfs file:
> /devices/system/cpu/cpu7/cache/index2/shared_cpu_map
>
On Sat, 2007-12-08 at 14:22 +0100, Andi Kleen wrote:
[39943.212533] [ cut here ]
[39943.221973] kernel BUG at fs/dcache.c:595!
[39943.230369] invalid opcode: [1] SMP
[39943.238638] last sysfs file:
/devices/system/cpu/cpu7/cache/index2/shared_cpu_map
On Monday 03 December 2007 16:23:58 Andi Kleen wrote:
>
> FYI
>
> Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
> but they're not changing anything near this AFAIK)
Got it again after rebooting the system. Can this be made a 2.6.24 blocker
or something?
On Monday 03 December 2007 16:23:58 Andi Kleen wrote:
FYI
Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
but they're not changing anything near this AFAIK)
Got it again after rebooting the system. Can this be made a 2.6.24 blocker
or something? Admittedly
On Mon, 3 Dec 2007 16:23:58 +0100
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> FYI
>
> Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
> but they're not changing anything near this AFAIK)
>
> -Andi
>
> [101109.104881] [ cut here ]
>
On Mon, 3 Dec 2007 16:23:58 +0100
Andi Kleen [EMAIL PROTECTED] wrote:
FYI
Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
but they're not changing anything near this AFAIK)
-Andi
[101109.104881] [ cut here ]
[101109.114487]
FYI
Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
but they're not changing anything near this AFAIK)
-Andi
[101109.104881] [ cut here ]
[101109.114487] kernel BUG at fs/dcache.c:595!
[101109.123053] invalid opcode: [1] SMP
FYI
Just saw this on a test system of mine running 2.4.24rc3 (+ some suse patches,
but they're not changing anything near this AFAIK)
-Andi
[101109.104881] [ cut here ]
[101109.114487] kernel BUG at fs/dcache.c:595!
[101109.123053] invalid opcode: [1] SMP
16 matches
Mail list logo
