Re: open() and cancellation - #123472

On Fri, 2005-08-05 at 19:01 -0500, Federico Mena Quintero wrote:

> Reload bug #123472 and you'll see some info.  I hadn't understood Dave
> and Alex's comments, but now I do.  Basically, you can also get canceled
> after open(2) returns, and the code doesn't handle that.
> I'm extracting some interesting debug logs after adding a bunch of
> printf()s, so I think I'll have it fixed soon.
> Now I delay the closing of canceled open()s until we are back in the
> dispatch_job_callback() for the main thread, since that is the only
> place where it can be done without race conditions.
> However, with my new patch the code accesses a structure that has
> already been freed - I'm investigating that.

The latest patch doesn't look right either. I added some comments to the
bug. It seems unlikely that we can get a large change like this in 2.12.

 Alexander Larsson                                            Red Hat, Inc 
                   alexl redhat com    alla lysator liu se 
He's a bookish white trash ex-con with a winning smile and a way with the 
ladies. She's a warm-hearted motormouth politician with someone else's 
memories. They fight crime! 

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