[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kernel panic in gsync_wait

From: Brent W. Baccala
Subject: Re: kernel panic in gsync_wait
Date: Fri, 4 Nov 2016 12:14:27 -1000

On Fri, Nov 4, 2016 at 12:00 AM, Samuel Thibault <samuel.thibault@gnu.org> wrote:
Brent W. Baccala, on Thu 03 Nov 2016 15:51:04 -1000, wrote:
> I see... so there must be fallback code (option 2 on my list); I just haven't
> found it.
> Where is KERN_FAILURE handled in user space?

It's not. Gsync_wait just returns, and the while loop just tries to take
the lock again.

Of course; it's designed to replace a spinlock!  Very clever.

Clever can cause problems, though.  We need to document this.

I've booted a new kernel and the weird ext2fs data corruption problems have gone away.

I'm currently working on a test case where I create a small ramdisk and fill it to exhaustion.  'dd' doesn't cleanly error out, though; it hangs.  I'm working through the error handling code in libpager (and friends) and have already found one problem, but there are others.

I guess I should file it as a bug.

How do we want to handle fixed bugs, like this gsync problem?  Should we open and close a bug report, just so it's documented in the bug database?  I can open the bug, of course, but I don't have permission to close it...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]