On Sun, 14 Aug 2005 21:20:35 -0600 (MDT)
Zwane Mwaikambo <[EMAIL PROTECTED]> wrote:
> On Sun, 14 Aug 2005, Robert Love wrote:
>
> > On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
> >
> > > I'm new here, if the inode isn't being watched, what's to stop d_delete
> > > from removing
On Sun, 14 Aug 2005 21:20:35 -0600 (MDT)
Zwane Mwaikambo [EMAIL PROTECTED] wrote:
On Sun, 14 Aug 2005, Robert Love wrote:
On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
I'm new here, if the inode isn't being watched, what's to stop d_delete
from removing the inode before
On Sun, 14 Aug 2005, Robert Love wrote:
> On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
>
> > I'm new here, if the inode isn't being watched, what's to stop d_delete
> > from removing the inode before fsnotify_unlink proceeds to use it?
>
> Nothing. But check out
>
>
On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
> I'm new here, if the inode isn't being watched, what's to stop d_delete
> from removing the inode before fsnotify_unlink proceeds to use it?
Nothing. But check out
On Sun, 14 Aug 2005, Phil Dier wrote:
> I just got this:
>
> Unable to handle kernel paging request at virtual address eeafefc0
> printing eip:
> c0188487
> *pde = 00681067
> *pte = 2eafe000
> Oops: [#1]
> SMP DEBUG_PAGEALLOC
> Modules linked in:
> CPU:1
> EIP:0060:[]Not
I just got this:
Unable to handle kernel paging request at virtual address eeafefc0
printing eip:
c0188487
*pde = 00681067
*pte = 2eafe000
Oops: [#1]
SMP DEBUG_PAGEALLOC
Modules linked in:
CPU:1
EIP:0060:[]Not tainted VLI
EFLAGS: 00010296 (2.6.13-rc6)
EIP is at
I just got this:
Unable to handle kernel paging request at virtual address eeafefc0
printing eip:
c0188487
*pde = 00681067
*pte = 2eafe000
Oops: [#1]
SMP DEBUG_PAGEALLOC
Modules linked in:
CPU:1
EIP:0060:[c0188487]Not tainted VLI
EFLAGS: 00010296 (2.6.13-rc6)
EIP is at
On Sun, 14 Aug 2005, Phil Dier wrote:
I just got this:
Unable to handle kernel paging request at virtual address eeafefc0
printing eip:
c0188487
*pde = 00681067
*pte = 2eafe000
Oops: [#1]
SMP DEBUG_PAGEALLOC
Modules linked in:
CPU:1
EIP:0060:[c0188487]Not tainted
On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
I'm new here, if the inode isn't being watched, what's to stop d_delete
from removing the inode before fsnotify_unlink proceeds to use it?
Nothing. But check out
On Sun, 14 Aug 2005, Robert Love wrote:
On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
I'm new here, if the inode isn't being watched, what's to stop d_delete
from removing the inode before fsnotify_unlink proceeds to use it?
Nothing. But check out
On Fri, Aug 12, 2005 at 12:35:05PM -0500, Phil Dier wrote:
> On Fri, 12 Aug 2005 12:07:21 +1000
> Neil Brown <[EMAIL PROTECTED]> wrote:
> > You could possibly put something like
> >
> > struct bio_vec *from;
> > int i;
> > bio_for_each_segment(from, bio, i)
> >
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown <[EMAIL PROTECTED]> wrote:
> You could possibly put something like
>
> struct bio_vec *from;
> int i;
> bio_for_each_segment(from, bio, i)
> BUG_ON(page_zone(from->bv_page)==NULL);
>
> in generic_make_requst in
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown [EMAIL PROTECTED] wrote:
You could possibly put something like
struct bio_vec *from;
int i;
bio_for_each_segment(from, bio, i)
BUG_ON(page_zone(from-bv_page)==NULL);
in generic_make_requst in
On Fri, Aug 12, 2005 at 12:35:05PM -0500, Phil Dier wrote:
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown [EMAIL PROTECTED] wrote:
You could possibly put something like
struct bio_vec *from;
int i;
bio_for_each_segment(from, bio, i)
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown <[EMAIL PROTECTED]> wrote:
> On Thursday August 11, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I posted an oops a few days ago from 2.6.12.3 [1]. Here are the results
> > of my tests on 2.6.13-rc6. The kernel oopses, but it the box isn't
> >
On Thursday August 11, [EMAIL PROTECTED] wrote:
> Hi,
>
> I posted an oops a few days ago from 2.6.12.3 [1]. Here are the results
> of my tests on 2.6.13-rc6. The kernel oopses, but it the box isn't completely
> hosed; I can still log in and move around. It appears that the only things
> that
On Thursday August 11, [EMAIL PROTECTED] wrote:
Hi,
I posted an oops a few days ago from 2.6.12.3 [1]. Here are the results
of my tests on 2.6.13-rc6. The kernel oopses, but it the box isn't completely
hosed; I can still log in and move around. It appears that the only things
that are
On Fri, 12 Aug 2005 12:07:21 +1000
Neil Brown [EMAIL PROTECTED] wrote:
On Thursday August 11, [EMAIL PROTECTED] wrote:
Hi,
I posted an oops a few days ago from 2.6.12.3 [1]. Here are the results
of my tests on 2.6.13-rc6. The kernel oopses, but it the box isn't
completely
hosed;
18 matches
Mail list logo
