All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Feise <jfeise@feise.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Read errors from r/o-mounted reiser4
Date: Tue, 17 Jan 2006 08:56:25 -0800	[thread overview]
Message-ID: <43CD21B9.60801@feise.com> (raw)
In-Reply-To: <1137542900.6375.85.camel@tribesman.namesys.com>

Hello,

unfortunately, the patch did not help. I still get the same errors:

$: mount -o ro,remount /usr
$: make xconfig
  CHECK   qt
  HOSTCC  scripts/kconfig/kconfig_load.o
In file included from /usr/include/sys/types.h:133,
                 from /usr/include/stdlib.h:433,
                 from scripts/kconfig/kconfig_load.c:3:
/usr/include/time.h:418: error: stray '\22' in program
/usr/include/time.h:418: error: stray '\377' in program
/usr/include/time.h:418: error: stray '\34' in program
/usr/include/time.h:418: error: stray '\17' in program
/usr/include/time.h:418: error: stray '\21' in program
/usr/include/time.h:418: error: stray '\377' in program
/usr/include/time.h:418: error: stray '\36' in program
/usr/include/time.h:418: error: stray '\21' in program
/usr/include/time.h:418: error: stray '\22' in program
/usr/include/time.h:418: error: stray '\377' in program
...

/usr/include/time.h only has 417 lines.

-Joe

Vladimir V. Saveliev wrote on 01/17/06 16:08:

> Hello
> 
> Sorry for delayed answer. we had long holidays here.
> Please try whether attached patch fixes the problem.
> 
> On Mon, 2006-01-02 at 01:04 -0800, Joe Feise wrote:
>> Vladimir V. Saveliev wrote on 12/28/05 18:31:
>>
>>> Hello
>>>
>>> On Tue, 2005-12-27 at 21:25 -0800, Joe Feise wrote:
>>>> Hi,
>>>>
>>>> in one of my systems, I have /usr on a Reiser4 partition.
>>>> When I have that partition mounted read-only, I get errors whenever
>>>> I try to compile anything. Other programs that read from that partition also
>>>> seem to fail, but I don't get such nice output like the stuff from gcc.
>>>> I am currently using Slackware 10.2 with kernel 2.6.15-rc5-mm3, but I have
>>>> experienced the same problem with earlier kernels as well.
>>>> The output from a make menuconfig in the kernel source dir:
>>> Thanks for the report. We will take a look
>>>
>>>> $: make menuconfig
>>>>
>>>>   HOSTCC  scripts/kconfig/conf.o
>>>> In file included from /usr/include/bits/types.h:31,
>>>>
>>>>                  from /usr/include/ctype.h:28,
>>>>                  from scripts/kconfig/conf.c:6:
>>>> /usr/lib/gcc-lib/i486-slackware-linux/3.3.6/include/stddef.h:420: error: syntax
>>>> error before '}' token
>>
>> I thought about this a bit more, and decided to take a look at the stddef.h file.
>> As it turns out, the file has only 419 lines, so line 420 is past the end of the
>> file.
>> That indicates to me that there is possibly a buffer that doesn't get cleared if
>> the fs is mounted r/o (an optimization gone wrong, maybe?)
>>
>> -Joe


  reply	other threads:[~2006-01-17 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  5:25 Read errors from r/o-mounted reiser4 Joe Feise
2005-12-29  2:31 ` Vladimir V. Saveliev
2006-01-02  9:04   ` Joe Feise
2006-01-18  0:08     ` Vladimir V. Saveliev
2006-01-17 16:56       ` Joe Feise [this message]
2006-01-19  1:00         ` Vladimir V. Saveliev
2006-01-18 16:33           ` Joe Feise
2006-01-17 19:06       ` Hans Reiser

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=43CD21B9.60801@feise.com \
    --to=jfeise@feise.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.