linux-kernel - Re: Linux v2.6.18-rc3

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] [day] [month] [year] [list]

Date:	Wed, 02 Aug 2006 16:58:26 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Hubert Tonneau <hubert.tonneau@...lpliant.org>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: Linux v2.6.18-rc3

At Wed, 02 Aug 2006 18:35:26 GMT,
Hubert Tonneau wrote:
> 
> Takashi Iwai wrote:
> >
> > Do you really get Oops with 2.6.17-final, too?
> > AFAIK, there was a bug in the early 2.6.17-rc regarding OSS emulation,
> > but it got fixed in the later rc.
> 
> I confirm that the only oops I got was with 2.6.17-rc1
> 
> > The behavior of invalid O_* flag seems incompatible with the older
> > version.  Although I don't think it's totally wrong behavior, surely
> > better to keep the compatibility.  The patch below should fix it.
> 
> I don't care: I have changed my player.
> I also tend to agree that opening /dev/dsp read write was not a good
> idea, so I would not criticise the new behaviour.

Well, incompatibility is worse in most cases than rationality.
Could you test the patch really fixes your case, so that I can push it
to 2.6.17-stable tree?

> Each version of Linux 2.6 tend to break some softwares due to subtil
> changes. What is bad is that these changes tend to be not announced,
> but on the other hand the kernel mailing list is very responsive,
> so all in all it might be a reasonable way to go.

It was an unintentioal change, so it's not somthing to be announced ;)
It's a thing just to be fixed.


Takashi
-
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/