linux-kernel - Re: 3.14: WARNING: sysfs group ffffffff81c50ca0 not found for kobject 'target5:0:0'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5383DA98.5010300@techfak.uni-bielefeld.de>
Date:	Tue, 27 May 2014 02:21:44 +0200
From:	Robert Abel <rabel@...hfak.uni-bielefeld.de>
To:	linux-scsi@...r.kernel.org
CC:	linux-kernel@...r.kernel.org
Subject: Re: 3.14: WARNING: sysfs group ffffffff81c50ca0 not found for kobject
 'target5:0:0'

Hi Olaf,

On 16.05.2014 19:18, Olaf Hering wrote:
> I did unplug an USB stick by accident with 3.14.4, the result is this
> warning:
>
>
> [94414.233882] usb 1-3: USB disconnect, device number 4
> [94414.245377] scsi 5:0:0:0: rejecting I/O to offline device
> [94414.245383] scsi 5:0:0:0: killing request
> [94414.370354] FAT-fs (sdc1): unable to read boot sector to mark fs as 
> dirty
> [94414.370393] ------------[ cut here ]------------
> [94414.370400] WARNING: CPU: 2 PID: 3619 at fs/sysfs/group.c:216 
> sysfs_remove_group+0xa1/0xb0()
> [94414.370403] sysfs group ffffffff81c50ca0 not found for kobject 
> 'target5:0:0'
This [1] might fix the problem you encountered. I reckon one of your 
drivers exposes a binary attribute file in a named attribute group, 
which it tries to remove when being unloaded. However, the path it looks 
for this attribute file is likely wrong.

     [1] http://comments.gmane.org/gmane.linux.kernel/1684070
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/