All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Adrian Sandu <dexter@d3xt3r01.tk>, linux-ext4@vger.kernel.org
Subject: Re: possible bug ?
Date: Wed, 19 Sep 2012 11:35:18 -0500	[thread overview]
Message-ID: <5059F446.5010308@redhat.com> (raw)
In-Reply-To: <5059F32D.10005@redhat.com>

On 9/19/12 11:30 AM, Eric Sandeen wrote:
> On 9/19/12 11:26 AM, Theodore Ts'o wrote:
>> On Wed, Sep 19, 2012 at 10:13:46AM -0500, Eric Sandeen wrote:
>>> On 9/19/12 9:44 AM, Adrian Sandu wrote:
>>>> Hi people,
>>>>
>>>> While trying to delete a couple of files today, I got into this lil'
>>>> thingy. It first happened in mc, then at a reboot.
>>>
>>> Did you cut off a few lines before this?  Like one that said NULL pointer
>>> dereference, or BUG() at .... or something similar?
>>>
>>> I think we have a few reports of this in the fedora bugzilla, I don't
>>> think we've gotten to the bottom of it yet.
>>
>> The fix is in mainline, and backported to v3.5.3.  If Fedora's kernel
>> hasn't been updated to v3.5.3, it would be great if you could
>> encourage an update to get pushed out.
> 
> Hm I thought we had a similar bug on 3.5.3 so didn't think
> it was fixed.   let me check ... Nope sorry, it was older.
> 
> Thanks for the info, sorry I had missed it.

Actually argh, too many bugs.  ;)  I was thinking of 
https://bugzilla.redhat.com/show_bug.cgi?id=857618

which has been reported a few times, and hits a BUG() in 

1965 ext4_ext_put_in_cache(struct inode *inode, ext4_lblk_t block,
1966                         __u32 len, ext4_fsblk_t start)
1967 {
1968         struct ext4_ext_cache *cex;
1969         BUG_ON(len == 0);

but that's not what this reporter sees, sorry for the noise.

(Lukas pointed at upstream commit 31d4f3a2f3c73f279ff96a7135d7202ef6833f12
to avoid the BUG_ON but we still don't know the root cause I think).

Anyway, now I'm OT for this thread.

-Eric

  reply	other threads:[~2012-09-19 16:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 14:44 possible bug ? Adrian Sandu
2012-09-19 15:13 ` Eric Sandeen
2012-09-19 16:09   ` Dmitry Monakhov
2012-09-19 16:26   ` Theodore Ts'o
2012-09-19 16:30     ` Eric Sandeen
2012-09-19 16:35       ` Eric Sandeen [this message]
2012-09-19 16:50         ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2025-11-08 22:19 Possible bug? Jani Partanen
2025-11-10 13:49 ` Jani Nikula
2025-11-10 13:49   ` Jani Nikula
2025-11-10 18:10   ` Lucas De Marchi
2025-11-10 18:10     ` Lucas De Marchi
2025-11-11  7:02     ` Usyskin, Alexander
2025-11-11  7:02       ` Usyskin, Alexander
2025-11-11  8:06       ` Jani Nikula
2025-11-11  8:06         ` Jani Nikula
2025-11-11 10:58         ` Usyskin, Alexander
2025-11-11 10:58           ` Usyskin, Alexander
2025-11-12 14:57           ` Lucas De Marchi
2025-11-12 14:57             ` Lucas De Marchi
2025-11-14 16:22             ` Jani Partanen

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=5059F446.5010308@redhat.com \
    --to=sandeen@redhat.com \
    --cc=dexter@d3xt3r01.tk \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.