public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: Re: On current git head webservers stopped working
Date: Fri, 13 Jul 2007 06:52:04 -0700	[thread overview]
Message-ID: <f78025$m3u$1@sea.gmane.org> (raw)
In-Reply-To: <20070713093459.GB5328@kernel.dk>

Jens Axboe wrote:
> On Fri, Jul 13 2007, Gabriel C wrote:
>> Hello ,
>>
>> While doing some tests with 2.6.22-git2 ( at the time head
>> 4eb6bf6bfb580afaf1e1a1d30cba17a078530cf4 ) all my webservers stopped
>> working.
>> I can't get any file using wget or whatever else , everything hangs
>> after 1% forever.
>>
>> I bisected this and here the result:
>>
>> 534f2aaa6ab07cd71164180bc958a7dcde41db11 is first bad commit
>> commit 534f2aaa6ab07cd71164180bc958a7dcde41db11
>> Author: Jens Axboe <jens.axboe@oracle.com>
>> Date:   Fri Jun 1 14:52:37 2007 +0200
>>
>>     sys_sendfile: switch to using ->splice_read, if available
...

> Does this work?
<patch snipped>

Hi Jens,
I was hoping this patch would fix a different problem caused by the
same merge of 'splice-2.6.23' three days ago, but it didn't.

When I run nfsd on the latest git kernel, it serves up what seems to
be the wrong inodes for every fetched file.  I can navigate the served
directory structure with no problems, but the contents of any file I
fetch are completely unrelated to the real contents.

Does this suggest a possible cause or fix?

Thanks.



  parent reply	other threads:[~2007-07-13 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13  9:28 On current git head webservers stopped working Gabriel C
2007-07-13  9:34 ` Jens Axboe
2007-07-13  9:49   ` Gabriel C
2007-07-13 10:00     ` Jens Axboe
2007-07-13 10:05       ` Christoph Hellwig
2007-07-13 11:00         ` Jens Axboe
2007-07-13 10:09       ` Gabriel C
2007-07-13 11:11         ` Jens Axboe
2007-07-13 13:52   ` walt [this message]
2007-07-13 17:27   ` Linus Torvalds
2007-07-13 17:39     ` Jens Axboe
2007-07-13 18:17       ` 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='f78025$m3u$1@sea.gmane.org' \
    --to=wa1ter@myrealbox.com \
    --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