Re: [1/3] 2.6.21-rc7: known regressions (v2)

Adrian Bunk <[email protected]> writes:

> On Tue, Apr 24, 2007 at 05:51:11PM -0700, Greg KH wrote:
>> On Wed, Apr 25, 2007 at 02:29:58AM +0200, Adrian Bunk wrote:
>> > On Tue, Apr 24, 2007 at 05:14:28PM -0700, Greg KH wrote:
>> > > On Tue, Apr 24, 2007 at 11:32:53AM +0200, Wolfgang Erig wrote:
>> > > > On Mon, Apr 23, 2007 at 03:18:19PM -0700, Greg KH wrote:
>> > > > > On Mon, Apr 23, 2007 at 11:48:47PM +0200, Adrian Bunk wrote:
>> > > > > > This email lists some known regressions in Linus' tree compared to
> 2.6.20.
>> > > > > > 
>> > > > > > If you find your name in the Cc header, you are either submitter of
> one
>> > > > > > of the bugs, maintainer of an affectected subsystem or driver, a
> patch
>> > > > > > of you caused a breakage or I'm considering you in any other way
>> > > > > > possibly involved with one or more of these issues.
>> > > > > > 
>> > > > > > Due to the huge amount of recipients, please trim the Cc when
> answering.
>> > > > > > 
>> > > > > > 
>> > > > > > Subject    : gammu no longer works
>> > > > > > References : http://lkml.org/lkml/2007/4/20/84
>> > > > > > Submitter  : Wolfgang Erig <[email protected]>
>> > > > > > Status     : unknown
>> > > > > 
>> > > > > I've asked for more information about this, and so far am not sure
> it's
>> > > > > a real problem.
>> > > > 
>> > > > It is a real problem for me.
>> > > > I tried this on 2 different boxes with the same behaviour.
>> > > > No sync between my Nokia mobile and Linux with the latest kernel :(
>> > > 
>> > > Sorry, I didn't see your response, have followed up on lkml now.
>> > 
>> > It turned out this was actually a bug in Gammu that will be fixed in 
>> > the next release of Gammu.
>> 
>> Ah, ok, thanks for letting me know.
>> 
>> But how was the kernel version change triggering it?
>
> I don't know, perhaps a side effect of Eric's work in kernel/signal.c?

Perhaps there has been a bit of churn.  Most of what I have done has
been fixing corner cases like not sending a signal to the wrong task,
after our original target has exited.

Although in conjunction with Oleg and some others there has been things
like changing locking to rcu or making locks more local so the timing
may have changed.  Which is make some subtle timing thing my best
guess.  For timing changes just about anything could have triggered
something.

I took a quick glance at the code and I certainly touched some of
the helpers like send_sigio that seem to be called by fasync
processing but I haven't a clue what FASYNC really does.  So I'm
having trouble putting this all into perspective.

I guess it's possible I fixed something without realizing it.


Eric

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel