d on it, and it's not yet apparent
>> to me what happened with this one.
>
> I researched bit the lists, and there was the inclusion request on the
> stable list itself. Looking into the io-uring list I found
> https://lore.kernel.org/io-uring/CADZouDRFJ9jtXHqkX-PTKeT=gxswdmc42zesakr34psug9t...@mail.gmail.com/
> which I think was the trigger to later on include in fact the commit
> in 6.1.120.
Yep indeed, was just looking for the backstory and that is why it got
backported. Just missed the fact that it should've been an
io_cqring_wake() rather than __io_cqring_wake()...
--
Jens Axboe
; As a start I set the above issue as a forward, to have the issues
>> linked (and we later on can update it to the linux upstream report).
>
> I suspect this might be introduced by one of the io_uring related
> changes between 6.1.119 and 6.1.123.
>
> But we need to be abl
On Sun, Oct 15 2006, Georg Wittenburg wrote:
> On Tuesday 10 October 2006 09:31, Jens Axboe wrote:
> > On Tue, Oct 10 2006, Oleg Verych wrote:
> > > Jens, please, help to sort out this one. 2.6.19-rc1 was tested with no
> > > luck.
> > >
> > > Bug
so far, I'd suggest you start
git bisecting with 2.6.16 as the good kernel and 2.6.17 as the bad
kernel to try and narrow the breakage point down a bit.
--
Jens Axboe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[ide_core]
> > ide_setup_pci_device+0x62/0x6d [ide_core]
> > pci_device_probe+0x36/0x57
> > driver_probe_device+0x42/0x8b
> > __driver_attach+0x38/0x5d bus_for_each_dev+0x33/0x55
> > driver_attach+0x11/0x13 __driver_attach+0x0/0x5d
> > bus_add_dr
5 matches
Mail list logo
