linux-kernel - Re: [Bugme-new] [Bug 7065] New: Devices no longer automount

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-next>] [day] [month] [year] [list]

Message-Id: <20060828121057.035fd690.akpm@osdl.org>
Date:	Mon, 28 Aug 2006 12:10:57 -0700
From:	Andrew Morton <akpm@...l.org>
To:	linux-kernel@...r.kernel.org
Cc:	Greg KH <greg@...ah.com>, Kay Sievers <kay.sievers@...e.de>,
	Greg KH <greg@...ah.com>, andrew@...ital-domain.net
Subject: Re: [Bugme-new] [Bug 7065] New: Devices no longer automount

On Mon, 28 Aug 2006 10:00:12 -0700
bugme-daemon@...zilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=7065
> 
>            Summary: Devices no longer automount

A post-2.6.17 regression, nicely bisected down to a particular changeset
(thanks!).

Is anyone else hitting this?


>     Kernel Version: 2.6.18-rc5
>             Status: NEW
>           Severity: normal
>              Owner: other_other@...nel-bugs.osdl.org
>          Submitter: andrew@...ital-domain.net
> 
> 
> Most recent kernel where this bug did not occur:
> 2.6.17-git3
> 
> Distribution:
> Fedora Core 5
> 
> Hardware Environment:
> x86 UP (Athlon and P4)
> 
> Software Environment:
> FC5 + latest updates
> 
> Problem Description:
> When in GNOME and a USB storage device is plugged in, the device is no 
> longer mounted automatically. 
> 
> Steps to reproduce:
> When in GNOME, plug in a USB storage device e.g USB memory stick.
> 
> Seems uvents for the mount command are not being generated.
> 
> Last bit of output from udevmonitor for working kernel
> 
> UEVENT[1154789231.832312] add@...ock/sda
> UEVENT[1154789231.834681] add@...ock/sda/sda1
> UDEV [1154789231.836590] add@...ass/scsi_device/9:0:0:0
> UDEV [1154789231.933474] add@...ock/sda
> UDEV [1154789232.106892] add@...ock/sda/sda1
> UEVENT[1154789235.937510] mount@...ock/sda/sda1
> UDEV [1154789235.937510] mount@...ock/sda/sda1
> 
> Last of bit of output from non-working kernel
> 
> UEVENT[1154789364.586896] add@...ock/sda
> UEVENT[1154789364.586954] add@...ock/sda/sda1
> UEVENT[1154789364.586963] add@...ass/scsi_device/10:0:0:0
> UDEV [1154789364.598962] add@...ass/scsi_device/10:0:0:0
> UDEV [1154789364.719350] add@...ock/sda
> UDEV [1154789364.874149] add@...ock/sda/sda1
> 
> 
> This regression happened between 2.6.17-git3 and 2.6.17-git4
> 
> A GIT bisect led to the following culprit.
> 
> 53877d06d53a412d901bb323f080296c363d8b51 is first bad commit
> commit 53877d06d53a412d901bb323f080296c363d8b51
> Author: Kay Sievers <kay.sievers@...e.de>
> Date:   Tue Apr 4 20:42:26 2006 +0200
> 
>     [PATCH] Driver core: bus device event delay
> 
>     split bus_add_device() and send device uevents after sysfs population
> 
>     Signed-off-by: Kay Sievers <kay.sievers@...e.de>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
> 
> :040000 040000 468b93360ff68fb133558a84f609731ddc2d846a
> 4db81e3af789cb7c0c3faea57a9f36ffa00732c3 M      drivers
> 
> 
> Reverting this patch fix'd the problem. Seems though that this is not the ideal
> solution.
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
-
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/