linux-kernel - Re: [PATCH 5/5] staging: et131x: Fix free IRQ from IRQ context warning after tx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Aug 2011 22:07:10 +0100
From:	Mark Einon <mark.einon@...il.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Greg KH <greg@...ah.com>, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org, o.hartmann@...ovital.com
Subject: Re: [PATCH 5/5] staging: et131x: Fix free IRQ from IRQ context
 warning after tx_timeout

On 23 August 2011 22:03, Greg KH <gregkh@...e.de> wrote:
> On Tue, Aug 23, 2011 at 09:43:31PM +0100, Mark Einon wrote:
>> On 23 August 2011 19:50, Greg KH <greg@...ah.com> wrote:
>> > On Tue, Aug 02, 2011 at 10:47:01PM +0100, Mark Einon wrote:
>> >> When a tx timeout occured, et131x_tx_timeout closed and re-opened the device to fix.
>> >> As et131x_close called free_irq(), bad things ensued (see warning trace below), namely a
>> >> storm of errors and warnings.
>> >> Fixed by replacing the close() and open() calls with just the relevant functions previously
>> >> called from these.
>> >> Verified on an ET-1310 device.
>> >>
>> >> Signed-off-by: Mark Einon <mark.einon@...il.com>
>> >
>> > This patch breaks the build :(
>> >
>> > Care to resend this one, and any other patch you have sent me but I
>> > didn't apply yet, again, as I have now applied all et131x patches in my
>> > queue.
>>
>> Hi Greg,
>>
>> I seem to have some difficulty updating my staging-next branch at the
>> moment, this method worked a few days ago. Am I doing something
>> idiotic, or is the issue with the remote?
>> The file refs/heads/staging-next contains
>> 4024bc73b1d1d8f82518b67b0996cb7b870dd1d4, which git doesn't seem to
>> like.
>>
>> [mark@...lap staging-2.6]$ git checkout staging-next
>> Already on 'staging-next'
>> [mark@...lap staging-2.6]$ git pull
>> remote: error: refs/heads/staging-next does not point to a valid object!
>> remote: Counting objects: 21, done.
>> remote: Compressing objects: 100% (12/12), done.
>> remote: Total 14 (delta 12), reused 2 (delta 2)
>> Unpacking objects: 100% (14/14), done.
>> >From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6
>>    fcb8ce5..20cc799  staging-linus -> origin/staging-linus
>> Your configuration specifies to merge with the ref 'staging-next'
>> from the remote, but no such ref was fetched.
>
> That's odd.
>
> First, back up your patches somewhere.
>
> Then try deleting the local branch:
>        git checkout master
>        git branch -D staging-next
> and then re-creating it:
>        git pull
>        git checkout -t -b staging-next origin/staging-next
>
> And then work on adding your patches back.
>
> See if that works.

I tried cloning a new repo, with the same error message.
Five minutes later, it's now all working again.

I'm putting it down to some sort of server sync issue?

Cheers,

  Mark
>
> thanks,
>
> greg k-h
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/