All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
To: linux-fsdevel@vger.kernel.org, Pavel Ivanov <paivanof@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 3.1.0-rc4 oops when connecting iPod
Date: Sat, 3 Sep 2011 04:59:25 +0100 (BST)	[thread overview]
Message-ID: <1315022365.50883.YahooMailClassic@web29510.mail.ird.yahoo.com> (raw)
In-Reply-To: <CAG1a4ruWCARq5NLXSDo9Hmc6i2d5XDeuwJTKEqyeOm20hcO66A@mail.gmail.com>

--- On Sat, 3/9/11, Pavel Ivanov <paivanof@gmail.com> wrote:

> Hi,
> 
> With kernel 3.1.0-rc4 any attempt to connect iPod to USB
> leads to
> kernel oops. I'd say that stacktrace of the oops is pretty
> much random
> and not related to HFS. But I was able to get useful info
> from it when
> I recompiled with CONFIG_SLUB_DEBUG_ON=y. In this case I
> don't get
> oops but the following instead:

There are a few hfsplus related changes to do protection against invalid data like this, but may be there are more. It would be useful to have the output from your 
objdump -l -d hfsplus.ko | grep  -A 1000 '<hfsplus_fill_super>'
(the -l gives line numbers against the kernel tree, so would be useful if you run this against the ko there...)

> 
> [   81.508807] hfs: filesystem size too
> large.
> [   81.559295]
> =============================================================================
> [   81.656965] BUG kmalloc-4096: Invalid
> object pointer 0xffff880136160400
> [   81.735947]
> -----------------------------------------------------------------------------
> [   81.735948]
> [   81.851359] INFO: Slab 0xffffea0004d85800
> objects=7 used=7 fp=0x
>       (null) flags=0x2000000000004081
> [   81.965628] Pid: 2086, comm:
> ipod-set-info Not tainted 3.1.0-rc4+ #2
> [   81.965629] Call Trace:
> [   81.965636] 
> [<ffffffff8119359f>] slab_err+0xaf/0xd0
> [   81.965640] 
> [<ffffffff8119381f>] ? slab_pad_check+0xaf/0x1a0
> [   81.965644] 
> [<ffffffff8119719f>]
> free_debug_processing+0x1ef/0x310
> [   81.965647] 
> [<ffffffff811974ba>] __slab_free+0x1fa/0x490
> [   81.965653] 
> [<ffffffffa0516c4d>] ? hfsplus_fill_super+0x2ed/0x610
> [hfsplus]
> [   81.965656] 
> [<ffffffff81197a3c>] kfree+0x12c/0x150
> [   81.965660] 
> [<ffffffffa0516c4d>] hfsplus_fill_super+0x2ed/0x610
> [hfsplus]
> [   81.965665] 
> [<ffffffff81438771>] ?
> ioctl_internal_command.clone.4+0x61/0x1b0
> [   81.965671] 
> [<ffffffff8161fe9e>] ? _raw_spin_unlock+0xe/0x40
> [   81.965675] 
> [<ffffffff81195eb8>] ? deactivate_slab+0x578/0x750
> [   81.965679] 
> [<ffffffff811af3cb>] ? sget+0xab/0x480
> [   81.965683] 
> [<ffffffff8133f0c9>] ? put_dec+0x59/0x60
> [   81.965685] 
> [<ffffffff813407d1>] ? number.clone.2+0x311/0x350
> [   81.965690] 
> [<ffffffff8116bd7b>] ? pcpu_alloc_area+0x10b/0x2c0
> [   81.965693] 
> [<ffffffff81341b81>] ? vsnprintf+0x471/0x610
> [   81.965696] 
> [<ffffffff8116c639>] ? pcpu_alloc+0x399/0x9e0
> [   81.965699] 
> [<ffffffff81341dc4>] ? snprintf+0x34/0x40
> [   81.965702] 
> [<ffffffff8133ebc6>] ? strlcpy+0x46/0x60
> [   81.965707] 
> [<ffffffff8115bfb2>] ? register_shrinker+0x52/0x60
> [   81.965710] 
> [<ffffffff811afa26>] mount_bdev+0x1c6/0x210
> [   81.965714] 
> [<ffffffffa0516960>] ? hfsplus_iget+0x240/0x240
> [hfsplus]
> [   81.965718] 
> [<ffffffffa05160a5>] hfsplus_mount+0x15/0x20
> [hfsplus]
> [   81.965720] 
> [<ffffffff811b0547>] mount_fs+0x47/0x1c0
> [   81.965723] 
> [<ffffffff8116cc90>] ? __alloc_percpu+0x10/0x20
> [   81.965727] 
> [<ffffffff811ca383>] vfs_kern_mount+0x63/0xd0
> [   81.965731] 
> [<ffffffff811cb4d4>] do_kern_mount+0x54/0x110
> [   81.965734] 
> [<ffffffff811cd022>] do_mount+0x502/0x7e0
> [   81.965736] 
> [<ffffffff8116738b>] ? strndup_user+0x5b/0x80
> [   81.965739] 
> [<ffffffff811cd710>] sys_mount+0x90/0xe0
> [   81.965744] 
> [<ffffffff81627402>] system_call_fastpath+0x16/0x1b
> [   81.965746] FIX kmalloc-4096: Object at
> 0xffff880136160400 not freed
> 
> Following by 2 other bugs with the same stack trace.
> 
> (BTW, before oops first message "hfs: filesystem size too
> large"
> always appears twice.)
> 
> 
> Another question: is hfsplus supposed to work at all? I see
> it's
> marked as "Orphaned" in MAINTAINERS and on attempt to
> connect iPod
> with kernel 2.6.38.11 (standard kernel in Ubuntu 11.04) I
> still don't
> get it working. Although without oops I get the following
> messages:
> 
> [   65.479360] usb 2-3: new high speed USB
> device using ehci_hcd and address 4
> [   65.686470] usbcore: registered new
> interface driver uas
> [   65.706455] Initializing USB Mass Storage
> driver...
> [   65.706901] scsi4 : usb-storage 2-3:1.0
> [   65.707251] usbcore: registered new
> interface driver usb-storage
> [   65.707254] USB Mass Storage support
> registered.
> [   66.702320] scsi 4:0:0:0:
> Direct-Access     Apple   
> iPod
>   1.62 PQ: 0 ANSI: 0
> [   66.704537] sd 4:0:0:0: Attached scsi
> generic sg2 type 0
> [   66.809047] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.809930] sd 4:0:0:0: [sdb] Write
> Protect is off
> [   66.809935] sd 4:0:0:0: [sdb] Mode Sense:
> 68 00 00 08
> [   66.809938] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   66.885037] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.885933] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   66.979400]  sdb: [mac] sdb1 sdb2
> [   66.981940] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.982834] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   67.055808] sd 4:0:0:0: [sdb] Attached
> SCSI removable disk
> [   67.299357] sd 4:0:0:0: [sdb] Bad block
> number requested
> [   67.362982] hfs: unable to find HFS+
> superblock
> [   67.499457] sd 4:0:0:0: [sdb] Bad block
> number requested
> [   67.563085] hfs: unable to find HFS+
> superblock
> 
> 
> Thank you,
> Pavel
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

WARNING: multiple messages have this Message-ID (diff)
From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
To: linux-fsdevel@vger.kernel.org, Pavel Ivanov <paivanof@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 3.1.0-rc4 oops when connecting iPod
Date: Sat, 3 Sep 2011 04:59:25 +0100 (BST)	[thread overview]
Message-ID: <1315022365.50883.YahooMailClassic@web29510.mail.ird.yahoo.com> (raw)
In-Reply-To: <CAG1a4ruWCARq5NLXSDo9Hmc6i2d5XDeuwJTKEqyeOm20hcO66A@mail.gmail.com>

--- On Sat, 3/9/11, Pavel Ivanov <paivanof@gmail.com> wrote:

> Hi,
> 
> With kernel 3.1.0-rc4 any attempt to connect iPod to USB
> leads to
> kernel oops. I'd say that stacktrace of the oops is pretty
> much random
> and not related to HFS. But I was able to get useful info
> from it when
> I recompiled with CONFIG_SLUB_DEBUG_ON=y. In this case I
> don't get
> oops but the following instead:

There are a few hfsplus related changes to do protection against invalid data like this, but may be there are more. It would be useful to have the output from your 
objdump -l -d hfsplus.ko | grep  -A 1000 '<hfsplus_fill_super>'
(the -l gives line numbers against the kernel tree, so would be useful if you run this against the ko there...)

> 
> [   81.508807] hfs: filesystem size too
> large.
> [   81.559295]
> =============================================================================
> [   81.656965] BUG kmalloc-4096: Invalid
> object pointer 0xffff880136160400
> [   81.735947]
> -----------------------------------------------------------------------------
> [   81.735948]
> [   81.851359] INFO: Slab 0xffffea0004d85800
> objects=7 used=7 fp=0x
>       (null) flags=0x2000000000004081
> [   81.965628] Pid: 2086, comm:
> ipod-set-info Not tainted 3.1.0-rc4+ #2
> [   81.965629] Call Trace:
> [   81.965636] 
> [<ffffffff8119359f>] slab_err+0xaf/0xd0
> [   81.965640] 
> [<ffffffff8119381f>] ? slab_pad_check+0xaf/0x1a0
> [   81.965644] 
> [<ffffffff8119719f>]
> free_debug_processing+0x1ef/0x310
> [   81.965647] 
> [<ffffffff811974ba>] __slab_free+0x1fa/0x490
> [   81.965653] 
> [<ffffffffa0516c4d>] ? hfsplus_fill_super+0x2ed/0x610
> [hfsplus]
> [   81.965656] 
> [<ffffffff81197a3c>] kfree+0x12c/0x150
> [   81.965660] 
> [<ffffffffa0516c4d>] hfsplus_fill_super+0x2ed/0x610
> [hfsplus]
> [   81.965665] 
> [<ffffffff81438771>] ?
> ioctl_internal_command.clone.4+0x61/0x1b0
> [   81.965671] 
> [<ffffffff8161fe9e>] ? _raw_spin_unlock+0xe/0x40
> [   81.965675] 
> [<ffffffff81195eb8>] ? deactivate_slab+0x578/0x750
> [   81.965679] 
> [<ffffffff811af3cb>] ? sget+0xab/0x480
> [   81.965683] 
> [<ffffffff8133f0c9>] ? put_dec+0x59/0x60
> [   81.965685] 
> [<ffffffff813407d1>] ? number.clone.2+0x311/0x350
> [   81.965690] 
> [<ffffffff8116bd7b>] ? pcpu_alloc_area+0x10b/0x2c0
> [   81.965693] 
> [<ffffffff81341b81>] ? vsnprintf+0x471/0x610
> [   81.965696] 
> [<ffffffff8116c639>] ? pcpu_alloc+0x399/0x9e0
> [   81.965699] 
> [<ffffffff81341dc4>] ? snprintf+0x34/0x40
> [   81.965702] 
> [<ffffffff8133ebc6>] ? strlcpy+0x46/0x60
> [   81.965707] 
> [<ffffffff8115bfb2>] ? register_shrinker+0x52/0x60
> [   81.965710] 
> [<ffffffff811afa26>] mount_bdev+0x1c6/0x210
> [   81.965714] 
> [<ffffffffa0516960>] ? hfsplus_iget+0x240/0x240
> [hfsplus]
> [   81.965718] 
> [<ffffffffa05160a5>] hfsplus_mount+0x15/0x20
> [hfsplus]
> [   81.965720] 
> [<ffffffff811b0547>] mount_fs+0x47/0x1c0
> [   81.965723] 
> [<ffffffff8116cc90>] ? __alloc_percpu+0x10/0x20
> [   81.965727] 
> [<ffffffff811ca383>] vfs_kern_mount+0x63/0xd0
> [   81.965731] 
> [<ffffffff811cb4d4>] do_kern_mount+0x54/0x110
> [   81.965734] 
> [<ffffffff811cd022>] do_mount+0x502/0x7e0
> [   81.965736] 
> [<ffffffff8116738b>] ? strndup_user+0x5b/0x80
> [   81.965739] 
> [<ffffffff811cd710>] sys_mount+0x90/0xe0
> [   81.965744] 
> [<ffffffff81627402>] system_call_fastpath+0x16/0x1b
> [   81.965746] FIX kmalloc-4096: Object at
> 0xffff880136160400 not freed
> 
> Following by 2 other bugs with the same stack trace.
> 
> (BTW, before oops first message "hfs: filesystem size too
> large"
> always appears twice.)
> 
> 
> Another question: is hfsplus supposed to work at all? I see
> it's
> marked as "Orphaned" in MAINTAINERS and on attempt to
> connect iPod
> with kernel 2.6.38.11 (standard kernel in Ubuntu 11.04) I
> still don't
> get it working. Although without oops I get the following
> messages:
> 
> [   65.479360] usb 2-3: new high speed USB
> device using ehci_hcd and address 4
> [   65.686470] usbcore: registered new
> interface driver uas
> [   65.706455] Initializing USB Mass Storage
> driver...
> [   65.706901] scsi4 : usb-storage 2-3:1.0
> [   65.707251] usbcore: registered new
> interface driver usb-storage
> [   65.707254] USB Mass Storage support
> registered.
> [   66.702320] scsi 4:0:0:0:
> Direct-Access     Apple   
> iPod
>   1.62 PQ: 0 ANSI: 0
> [   66.704537] sd 4:0:0:0: Attached scsi
> generic sg2 type 0
> [   66.809047] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.809930] sd 4:0:0:0: [sdb] Write
> Protect is off
> [   66.809935] sd 4:0:0:0: [sdb] Mode Sense:
> 68 00 00 08
> [   66.809938] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   66.885037] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.885933] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   66.979400]  sdb: [mac] sdb1 sdb2
> [   66.981940] sd 4:0:0:0: [sdb] 1946049
> 4096-byte logical blocks:
> (7.97 GB/7.42 GiB)
> [   66.982834] sd 4:0:0:0: [sdb] Assuming
> drive cache: write through
> [   67.055808] sd 4:0:0:0: [sdb] Attached
> SCSI removable disk
> [   67.299357] sd 4:0:0:0: [sdb] Bad block
> number requested
> [   67.362982] hfs: unable to find HFS+
> superblock
> [   67.499457] sd 4:0:0:0: [sdb] Bad block
> number requested
> [   67.563085] hfs: unable to find HFS+
> superblock
> 
> 
> Thank you,
> Pavel
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-09-03  3:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03  3:08 Kernel 3.1.0-rc4 oops when connecting iPod Pavel Ivanov
2011-09-03  3:59 ` Hin-Tak Leung [this message]
2011-09-03  3:59   ` Hin-Tak Leung
2011-09-03  4:37   ` Pavel Ivanov
2011-09-03  6:57     ` Hin-Tak Leung
2011-09-03 20:52       ` Pavel Ivanov
2011-09-03 20:52         ` Pavel Ivanov
2011-09-03 23:35         ` Hin-Tak Leung
2011-09-03 23:35           ` Hin-Tak Leung
2011-09-03 23:59           ` Pavel Ivanov
2011-09-03 23:59             ` Pavel Ivanov
2011-09-04  0:37             ` Hin-Tak Leung
2011-09-06  4:35               ` Pavel Ivanov
2011-09-06  4:35                 ` Pavel Ivanov
2011-09-06  5:12                 ` Hin-Tak Leung
2011-09-06  5:12                   ` Hin-Tak Leung
2011-09-06 15:09                   ` Pavel Ivanov
2011-09-06 15:09                     ` Pavel Ivanov
2011-09-11  3:52                     ` Pavel Ivanov
2011-09-11  3:52                       ` Pavel Ivanov
2011-09-11 13:46                       ` Hin-Tak Leung
2011-09-11 13:46                         ` Hin-Tak Leung
2011-09-11 14:14                         ` Christoph Hellwig
2011-09-11 14:12                       ` Christoph Hellwig
2011-09-12 14:34                       ` Christoph Hellwig
2011-09-12 15:19                         ` Pavel Ivanov
2011-09-12 15:19                           ` Pavel Ivanov
2011-09-12 15:31                           ` Christoph Hellwig
2011-09-13  2:20                             ` Pavel Ivanov
2011-09-13  2:20                               ` Pavel Ivanov
2011-09-14 17:42                               ` Christoph Hellwig
2011-09-15 14:35                                 ` Christoph Hellwig
2011-09-12 15:57                           ` Hin-Tak Leung
2011-09-07 17:59                 ` Seth Forshee
2011-09-07 17:59                   ` Seth Forshee
2011-09-08  3:13                   ` Hin-Tak Leung
2011-09-08  3:13                     ` Hin-Tak Leung
2011-09-08 16:23                     ` Seth Forshee
2011-09-09 12:48                       ` Christoph Hellwig
2011-09-11  3:32                       ` Pavel Ivanov
2011-09-11  3:32                         ` Pavel Ivanov
2011-09-11 14:10                         ` Christoph Hellwig
2011-09-12 14:00                           ` Pavel Ivanov
2011-09-12 15:27                             ` [PATCH] hfsplus: Fix kfree of wrong vhdr pointers Seth Forshee
2011-09-12 15:28                               ` Christoph Hellwig

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=1315022365.50883.YahooMailClassic@web29510.mail.ird.yahoo.com \
    --to=hintak_leung@yahoo.co.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paivanof@gmail.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.