linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207327] New: Hang when reading encrypted DVD
Date: Fri, 17 Apr 2020 17:34:56 +0000	[thread overview]
Message-ID: <bug-207327-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=207327

            Bug ID: 207327
           Summary: Hang when reading encrypted DVD
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.5.15-200.fc31.x86_64
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: horsley1953@gmail.com
        Regression: No

This redhat bug has a huge collection of comments analyzing the problem.

https://bugzilla.redhat.com/show_bug.cgi?id=1822948

It comes down to two issues:

1. Reading an encrypted sector on a commercial movie DVD simply generates a
scsi error with a directly connected sata drive, but put that same drive in an
external USB enclosure and read the same sector, and the read seems to hang and
leave the drive unusable.

2. systemd-udevd apparently decides to randomly read sectors, thus causing the
drive to be useless as soon as you insert a movie DVD.

Probably udevd shouldn't be doing that, but it also seems like it should be
getting an error rather than a hung process, which seems like a kernel bug
(unless it is a fundamental flaw in usb enclosures. I tried two different ones
with the same results, though they may be using the same chipset).

Comment 99 in the redhat bug has a somewhat more detailed summary:

https://bugzilla.redhat.com/show_bug.cgi?id=1822948#c99

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

                 reply	other threads:[~2020-04-17 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-207327-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).