From: Jens Axboe <axboe@kernel.dk>
To: Mischa Baars <mjbaars1977.linux-block@cyberfiber.eu>,
Bart Van Assche <bvanassche@acm.org>,
Hannes Reinecke <hare@suse.de>,
linux-block@vger.kernel.org
Subject: Re: packet writing support
Date: Mon, 7 Oct 2019 10:19:39 -0600 [thread overview]
Message-ID: <e507eb38-becf-b6a5-bb51-14f873aca28d@kernel.dk> (raw)
In-Reply-To: <62ffa873794d2d6ced83bfc2a59d172677ef815c.camel@cyberfiber.eu>
On 10/7/19 10:13 AM, Mischa Baars wrote:
> On Mon, 2019-10-07 at 07:22 -0700, Bart Van Assche wrote:
>> On 2019-10-07 02:17, Mischa Baars wrote:
>>> On Mon, 2019-10-07 at 11:11 +0200, Mischa Baars wrote:
>>>> necesarry
>>>
>>> a) If necessary I could do the maintaining, sure.
>>
>> You may want to start with having a look at the following:
>> * pktcdvd: invalid opcode 0000 kernel BUG in pkt_make_request
>> (https://bugzilla.kernel.org/show_bug.cgi?id=201481)
>> * pktcdvd triggers a lock inversion complaint
>> (https://bugzilla.kernel.org/show_bug.cgi?id=202745)
>>
>> Thanks,
>>
>> Bart.
>
> I'm unable to reproduce these findings, also I'm unable to find any
> executable or any manpage called pktsetup.
Let's put this to rest. You are not using pktcdvd in your current setup.
You have apparently stumbled into some cdrom/dvd related regression if
the burning stopped working for you, please see:
Documentation/admin-guide/reporting-bugs.rst
in the kernel tree for how to report that bug, separately. No further
emails are needed in this thread.
--
Jens Axboe
next prev parent reply other threads:[~2019-10-07 16:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 10:12 packet writing support Mischa Baars
2019-10-05 15:50 ` Jens Axboe
2019-10-06 7:31 ` Mischa Baars
2019-10-06 15:10 ` Jens Axboe
2019-10-07 7:02 ` Mischa Baars
2019-10-07 7:23 ` Hannes Reinecke
2019-10-07 8:07 ` Mischa Baars
2019-10-07 8:45 ` Hannes Reinecke
2019-10-07 9:11 ` Mischa Baars
2019-10-07 9:17 ` Mischa Baars
2019-10-07 14:22 ` Bart Van Assche
2019-10-07 14:36 ` Mischa Baars
2019-10-07 16:13 ` Mischa Baars
2019-10-07 16:19 ` Jens Axboe [this message]
2019-10-07 17:31 ` Mischa Baars
2019-10-07 10:02 ` Hannes Reinecke
2019-10-07 14:10 ` Jens Axboe
2019-10-07 14:19 ` Mischa Baars
2019-10-06 8:31 ` Mischa Baars
2019-10-06 20:48 ` Laurence Oberman
2019-10-07 8:10 ` Mischa Baars
2019-10-07 9:02 ` Mischa Baars
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 9:22 Mischa Baars
2019-10-04 9:21 Mischa Baars
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=e507eb38-becf-b6a5-bb51-14f873aca28d@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=mjbaars1977.linux-block@cyberfiber.eu \
/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.