linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Jim Meyering <jim@meyering.net>, linux-ext4@vger.kernel.org
Subject: Re: rawhide's init/nash segfaults in libblkid
Date: Mon, 23 Feb 2009 16:52:34 -0600	[thread overview]
Message-ID: <49A328B2.7090503@redhat.com> (raw)
In-Reply-To: <20090223224219.GB3199@webber.adilger.int>

Andreas Dilger wrote:
> On Feb 23, 2009  17:41 +0100, Jim Meyering wrote:
>> FYI, I've just filed this against the kernel:
>>
>>   http://bugzilla.redhat.com/486997
>>
>> Perhaps it should be reassigned to e2fsprogs...
>> ---------
>>
>> Normally I track rawhide pretty closely, but for the last few weeks
>> new kernels haven't booted on the system I use for that, so I stuck
>> with the most recent one that worked,
> 
> Is rawhide using util-linux-ng that included the libblkid code?  It
> seems we probably need to add a configure check to e2fsprogs not to
> build libblkid if util-linux-ng has it.

Karel just sent a patch to do so (more or less), I think.

[PATCH] blkid: add --disable-libblkid to build with external libblkid

but AFAIK rawhide is still using e2fsprogs' blkid.  I'll look into it.

-Eric

  reply	other threads:[~2009-02-23 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 16:41 rawhide's init/nash segfaults in libblkid Jim Meyering
2009-02-23 22:42 ` Andreas Dilger
2009-02-23 22:52   ` Eric Sandeen [this message]
2009-02-24  7:59     ` Karel Zak

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=49A328B2.7090503@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --cc=jim@meyering.net \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).