mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Tue, 26 Sep 2023 11:11:23 +0200	[thread overview]
Message-ID: <f3d8c72b-cd30-490c-833f-5807bd74511f@kernel.org> (raw)
In-Reply-To: <20230704121847.GA26576@workstation.local>

Hi,

On 04. 07. 23, 14:18, Takashi Sakamoto wrote:
> Please pull firewire updates for v6.5-rc1.
> 
> The following changes since commit 44c026a73be8038f03dbdeef028b642880cf1511:
> 
>    Linux 6.4-rc3 (2023-05-21 14:05:48 -0700)

Likely some of the below commits causes an instant reboot during boot as 
was reported in:
   https://bugzilla.suse.com/show_bug.cgi?id=1215436

6.4.* was fine, 6.5.4 or 6.6-rc1 fails.

module_blacklist=firewire_ohci fixes the issue on 6.5.4.

Any ideas what can cause this? I fail to see an issue in the commits...

FWIW I see "obsolete usage of GFP_ATOMIC" was reverted in 6.5.5 and 
6.6-rc2, I asked the reporter to test those.

> Takashi Sakamoto (24):
>        firewire: add KUnit test to check layout of UAPI structures
>        firewire: cdev: add new version of ABI to notify time stamp at request/response subaction of transaction
>        firewire: cdev: add new event to notify request subaction with time stamp
>        firewire: cdev: implement new event to notify request subaction with time stamp
>        firewire: core: use union for callback of transaction completion
>        firewire: core: implement variations to send request and wait for response with time stamp
>        firewire: cdev: code refactoring to operate event of response
>        firewire: cdev: add new event to notify response subaction with time stamp
>        firewire: cdev: implement new event to notify response subaction with time stamp
>        firewire: cdev: code refactoring to dispatch event for phy packet
>        firewire: cdev: add new event to notify phy packet with time stamp
>        firewire: cdev: implement new event relevant to phy packet with time stamp
>        firewire: fix build failure due to missing module license
>        firewire: fix warnings to generate UAPI documentation
>        firewire: ohci: use devres for memory object of ohci structure
>        firewire: ohci: use devres for PCI-related resources
>        firewire: ohci: use devres for MMIO region mapping
>        firewire: ohci: use devres for misc DMA buffer
>        firewire: ohci: use devres for requested IRQ
>        firewire: ohci: use devres for list of isochronous contexts
>        firewire: ohci: use devres for IT, IR, AT/receive, and AT/request contexts
>        firewire: ohci: use devres for content of configuration ROM
>        firewire: ohci: release buffer for AR req/resp contexts when managed resource is released
>        firewire: core: obsolete usage of GFP_ATOMIC at building node tree
> 
> Zhang Shurong (1):
>        firewire: net: fix use after free in fwnet_finish_incoming_packet()

thanks,
-- 
js
suse labs


  parent reply	other threads:[~2023-09-26  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 12:18 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26  9:11 ` Jiri Slaby [this message]
2023-09-26 14:09   ` Takashi Sakamoto
2023-09-27  5:03     ` Jiri Slaby
2023-10-01  5:15       ` Takashi Sakamoto
2023-10-02 10:42         ` Jiri Slaby
2023-10-04  0:24           ` Takashi Sakamoto
2023-10-04  8:33             ` Jiri Slaby
2023-10-16 15:56               ` Takashi Sakamoto
2023-10-17  7:36                 ` Jiri Slaby
2023-09-27 13:15   ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04     ` Linux regression tracking #update (Thorsten Leemhuis)

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=f3d8c72b-cd30-490c-833f-5807bd74511f@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®