From: Greg KH <firstname.lastname@example.org> To: Dio Putra <email@example.com> Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: USB Attached SCSI breakage due no udev involvement Date: Sun, 10 May 2020 08:54:16 +0200 [thread overview] Message-ID: <20200510065416.GA3434442@kroah.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Sun, May 10, 2020 at 01:48:24PM +0700, Dio Putra wrote: > On 5/10/20 12:47 PM, Greg KH wrote: > > On Sun, May 10, 2020 at 09:55:57AM +0700, Dio Putra wrote: > >> Hi, it's first time for me to report user-space breakage in here, so > >> i'm begging your pardon. > >> > >> I want to report that Linux 5.4 breaking my USB mount workflow due > >> udevadm monitor report here (I'm using vanilla kernel 5.4.39 on > >> Slackware64 Current and vanilla kernel 4.4.221 on Slackware64 14.2): > > > > <snip> > > > > Sorry, but what actually changed that you can see in the logs? > Sorry, what do you mean? The dmesg log or the kernel changelogs? Either, your message made them pretty impossible to compare with all of the line-wrapping :( > > What functionality broke? What used to work that no longer does work? > > > Yes, it supposed that just work and kernel could talk with udev, not just handled by the kernel. I don't understand, what functionality changed? What exactly used to work that no longer does? Did you change anything else other than the kernel on your system? Did you change to a newer version of udev/systemd or anything else? thanks, greg k-h
next prev parent reply other threads:[~2020-05-10 6:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-10 2:55 Dio Putra 2020-05-10 5:47 ` Greg KH 2020-05-10 6:48 ` Dio Putra 2020-05-10 6:54 ` Greg KH [this message] 2020-05-10 7:10 ` Dio Putra 2020-05-10 7:32 ` Greg KH 2020-05-10 8:35 ` Dio Putra 2020-05-10 8:48 ` Greg KH 2020-05-10 9:48 ` Dio Putra 2020-05-10 13:15 ` Dio Putra
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=20200510065416.GA3434442@kroah.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: USB Attached SCSI breakage due no udev involvement' \ /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
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.