public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: sshd segmentation fault on ia64 on 28-rc7-mmotm-081203 -	bisected
Date: Thu, 18 Dec 2008 20:54:04 +0100	[thread overview]
Message-ID: <494AAA5C.6060601@gmail.com> (raw)
In-Reply-To: <1228940487.6139.68.camel@lts-notebook>

Hello,

[ Sorry for the late reply ]

Lee Schermerhorn wrote:
> On Wed, 2008-12-03 at 11:43 -0500, Lee Schermerhorn wrote:
>> I couldn't find anything on the list about this.
>>
>> I've built and booted 28-rc7-mmotm-081203 on both x86_64 and ia64.  I
>> can ssh into the x86_64 platform fine.  On the ia64, I'm seeing sshd
>> [from RHEL5 distro] seg faulting.  [Same sshd worked on the
>> 28-rc6-mmotm-081201 kernel.]
>>
>> Has anyone else seen this?
>>
> 
> I finally got around to bisecting this--sshd fails with SEGV on ia64--on
> mmotm-081208.  It appears to be caused by the patch duo:
> 
> do_mpage_readpage-remove-first_logical_block-parameter.patch
> do_mpage_readpage-remove-first_logical_block-parameter-fix.patch

Unfortunately I don't see why this patch causes such breakage.

Could you apply the following patch with the previous patch applied
and see if sshd still segfaults ?

It basically reverts:

   do_mpage_readpage-remove-first_logical_block-parameter-fix.patch

Therefore I can see which part of the patch is broken.

Also can you tell me what the block size used by the file system
hosting sshd ?

Thanks !

                Franck

--- 8< ---

diff --git a/fs/mpage.c b/fs/mpage.c
index ca33b28..b5ac1ff 100644
--- a/fs/mpage.c
+++ b/fs/mpage.c
@@ -163,10 +163,7 @@ map_buffer_to_page(struct page *page, struct buffer_head *bh, int page_block)
 */
 static int last_mapped_page(struct buffer_head *map_bh, struct page *page)
 {
-	pgoff_t map_index = map_bh->b_page->index;
-
-	return buffer_boundary(map_bh) &&
-		page->index >= map_index + (map_bh->b_size>>PAGE_CACHE_SHIFT);
+	return buffer_boundary(map_bh);
 }
 
 /*

  parent reply	other threads:[~2008-12-18 19:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 16:43 sshd segmentation fault on ia64 on 28-rc7-mmotm-081203 Lee Schermerhorn
2008-12-04  5:16 ` KOSAKI Motohiro
2008-12-10 20:21 ` sshd segmentation fault on ia64 on 28-rc7-mmotm-081203 - bisected Lee Schermerhorn
2008-12-10 20:29   ` Andrew Morton
2008-12-18 19:54   ` Franck Bui-Huu [this message]
2008-12-18 20:05     ` Lee Schermerhorn
2008-12-18 21:33       ` Franck Bui-Huu

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=494AAA5C.6060601@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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