The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Paul Albrecht <albrecht@rdi1.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: unionfs and sys_readahead
Date: Wed, 7 Nov 2007 19:53:25 +0000	[thread overview]
Message-ID: <200711071953.25716.vda.linux@googlemail.com> (raw)
In-Reply-To: <1194386482.7489.5.camel@albrecht.rdi1.com>

On Tuesday 06 November 2007 22:01, Paul Albrecht wrote:
> Hi,
> 
> Whenever I use readahead-list on a union mounted file system I get a
> segfault and kernel oops so I'm wondering whether or not the linux
> unionfs supports sys_readahead.
> 
> Anyone know? I'm not usually subscribed to the lkml so please cc me in
> your response. Thanks.

Please show actual oops output.

Also: what kernel version do you use? any extra patch(es) applied? .config?
--
vda

  reply	other threads:[~2007-11-07 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 22:01 unionfs and sys_readahead Paul Albrecht
2007-11-07 19:53 ` Denys Vlasenko [this message]
2007-11-07 20:43   ` Paul Albrecht
2007-11-09  2:11     ` Erez Zadok

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=200711071953.25716.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=albrecht@rdi1.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