From: "Torsten Kaiser" <just.for.lkml@googlemail.com>
To: "Matt Mackall" <mpm@selenic.com>
Cc: "Tejun Heo" <htejun@gmail.com>, "Jeff Garzik" <jeff@garzik.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: sata_sil24 broken since 2.6.23-rc4-mm1
Date: Wed, 3 Oct 2007 19:36:55 +0200 [thread overview]
Message-ID: <64bb37e0710031036q228b63a8nf03d030b7d97b27f@mail.gmail.com> (raw)
In-Reply-To: <20071003163804.GR19691@waste.org>
On 10/3/07, Matt Mackall <mpm@selenic.com> wrote:
> On Wed, Oct 03, 2007 at 05:55:10PM +0200, Torsten Kaiser wrote:
> > This patch removes clear_refs_smap() from fs/proc/task_mmu.c by moving
> > its code to a new function. But during the move the main for-loop from
> > clear_refs_smap was changed:
> >
> > old:
> > for (vma = mm->mmap; vma; vma = vma->vm_next)
> > if (vma->vm_mm && !is_vm_hugetlb_page(vma))
> > walk_page_range(vma->vm_mm, vma->vm_start, vma->vm_end,
> > &clear_refs_walk, vma);
> >
> > new:
> > for (vma = mm->mmap; vma; vma = vma->vm_next)
> > if (!is_vm_hugetlb_page(vma))
> > walk_page_range(mm, vma->vm_start, vma->vm_end,
> > &clear_refs_walk, vma);
> >
> > The walk_page_range() is no longer called on vma->vm_mm, but on mm directly.
> > I don't know how this can kill the sata_sil24-driver, but at least it
> > looks suspicious.
>
> That code should be fine. Further, it's pretty unlikely that this code
> ever gets invoked. This whole interface was only recently added by
> Google folks and its usage is pretty obscure.
>
> Oh wait - you're _at_ Google, aren't you? Perhaps you're actually
> using clear_refs.
No. I'm just using Google Mail.
And I'm not using any additional patches apart from what is in the mm-patchset.
> 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_hugetlb_page(vma)) {
> if (vma->vm_mm != mm)
> printk("WTF: vma->vm_mm %p mm %p\n",
> vma->vm_mm, mm);
> walk_page_range(vma->vm_mm, vma->vm_start, vma->vm_end,
> &clear_refs_walk, vma);
> }
Will try this, but as the error only seems to trigger, if I leave the
pc powered off for more then a hour, you will need to wait until
tomorrow.
Of note might be, that at the time of this error init has not been
started. I'm using a program from initramfs to start the RAID.
The initramfs was primarily build using the genkernel package from
gentoo, but I have removed some parts of it (kernel modules and some
other part I no longer remember)
Torsten
next prev parent reply other threads:[~2007-10-03 17:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 20:26 Torsten Kaiser
2007-09-27 4:54 ` Tejun Heo
2007-09-27 4:57 ` Tejun Heo
2007-09-27 6:14 ` Torsten Kaiser
2007-09-27 6:24 ` Jeff Garzik
2007-09-27 17:34 ` Torsten Kaiser
2007-09-27 20:22 ` Tejun Heo
2007-09-28 5:36 ` Torsten Kaiser
2007-09-30 6:00 ` Torsten Kaiser
2007-09-30 14:34 ` Tejun Heo
2007-09-30 16:19 ` Torsten Kaiser
2007-09-30 17:39 ` Tejun Heo
2007-09-30 18:39 ` Torsten Kaiser
2007-10-01 18:00 ` Torsten Kaiser
2007-10-03 15:21 ` Torsten Kaiser
2007-10-03 15:55 ` Torsten Kaiser
2007-10-03 16:38 ` Matt Mackall
2007-10-03 17:36 ` Torsten Kaiser [this message]
2007-10-03 17:51 ` Matt Mackall
2007-10-03 18:06 ` Torsten Kaiser
2007-10-04 5:32 ` Torsten Kaiser
2007-10-04 17:05 ` Matt Mackall
2007-10-05 6:06 ` Torsten Kaiser
2007-10-07 8:44 ` Torsten Kaiser
2007-10-07 14:39 ` Torsten Kaiser
2007-10-11 3:25 ` Tejun Heo
2007-10-11 5:54 ` Torsten Kaiser
2007-10-11 6:26 ` Tejun Heo
2007-10-11 17:51 ` Torsten Kaiser
2007-10-11 8:26 ` Jens Axboe
2007-10-11 8:36 ` Tejun Heo
2007-10-11 10:28 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64bb37e0710031036q228b63a8nf03d030b7d97b27f@mail.gmail.com \
--to=just.for.lkml@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®