[stable] [patch 00/50] -stable review

[stable] [patch 00/50] -stable review

Post by Greg K » Wed, 07 Feb 2007 06:50:11



It was dropped a while ago, sorry.

I'll go through the archives and see if there's enough to do a .18
release (and the patches are serious enough to warrent it.)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Chris Wrig » Wed, 07 Feb 2007 07:20:12


Not quite. It's more of a "some overlap," so that as soon as 2.6.x
comes out we don't instantly drop 2.6.(x-1).y stream. But we don't keep
it going, typically more 1 or 2 2.6.(x-1).y releases once 2.6.x is out.


I had actually queued them up, but we only had 1 or 2 other patches,
and they weren't significant enough to warrant flushing that queue.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/

 
 
 

[stable] [patch 00/50] -stable review

Post by Greg K » Wed, 07 Feb 2007 07:30:16


I'll see if the latest stuff that is queued up and some other stuff is
worth to push out a new release in a few days.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Michael Kr » Wed, 07 Feb 2007 07:30:17


Actually, I have a few more -stable patches for both 2.6.18.y and 2.6.19.y, if
you don't mind holding off a day or two (wont have time to prepare these until
tomorrow evening)... One of them is a security fix, that allows a non-root user
to hang the kernel given the correct circumstances.

Maybe you guys can make some sort of announcement before the -stable kernel is
closed. I know that now that 2.6.20 is released, implicitly 2.6.18.y is
closed... but it's been a long while since the last 2.6.18.y release, so I
wasn't sure if patches were still being accepted.

Regards,

Michael Krufky

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Greg K » Wed, 07 Feb 2007 07:40:05


Ok, that's serious enough :)

I'll wait for your patches.


I thought we did at the time we did the last release, but I'll try to
remember to highlight it a more prominently next time.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Michael Kr » Fri, 09 Feb 2007 06:20:11


I've uploaded the remaining pending v4l/dvb -stable patches for both 2.6.18.y
and 2.6.19.y to the following locations:

http://www.yqcomputer.com/ ~mkrufky/stable/2.6.18.y/ (8 patches)

and

http://www.yqcomputer.com/ ~mkrufky/stable/2.6.19.y/ (5 patches)

Using the mailer at my current location, I am unable to send patches inline, and
I won't have the time for it this evening. In the interest of saving time, I
figured that sending them to you in this method is good enough. If you still
need for me to send them via email inline, please let me know.

Best Regards,

Michael Krufky

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Michael Kr » Sun, 11 Feb 2007 04:50:18


Greg & Chris,

I haven't heard from either of you about these patches, nor have I seen any
update to the stable-queue.

Just for clarification, the security fix patch, that prevents a non-root user
from *** the kernel is the patch entitled,

"V4L: buf_qbuf: fix videobuf_queue->stream corruption and lockup"

...as per Mauro's description, here:

http://www.yqcomputer.com/ @XXXXX.COM /msg113820.html

Regards,

Michael Krufky

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Greg K » Sun, 11 Feb 2007 05:00:13


Thanks, I'll be flushing out the stable queue later on tonight and will
pick up all of these patches.

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Greg K » Thu, 22 Feb 2007 08:20:11


Ok, I've now gotten all of these for .19 and .18.

If I've missed anything, please let me know.

thanks for your patience.

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/
 
 
 

[stable] [patch 00/50] -stable review

Post by Michael Kr » Thu, 22 Feb 2007 11:40:09


Looks good... Thank you, Greg.



Normally, I would wait for a patch to appear in Linus' tree before I send it to -stable,
however, this patch can not wait. Since 2.6.18-stable and 2.6.19-stable have their last
releases pending review, it is imperative that this final patch be added to the queue, if
possible.

This patch was recently submitted, and fixes many horrible, previously unexplained bugs of the
past.

Please queue this for the final 2.6.18 and 2.6.19 -stable releases, as well as for 2.6.20.1

Thank you,

Michael Krufky

---

dvbdev: fix illegal re-usage of fileoperations struct

From: Marcel Siegert < XXXX@XXXXX.COM >

Arjan van de Ven < XXXX@XXXXX.COM > reported an illegal re-usage of the fileoperations struct
if more than one dvb device(e.g. frontend) is present. this patch fixes this issue.
it allocates a new fileoperations struct each time a device is registered and copies the default
template fileops.

Signed-off-by: Marcel Siegert < XXXX@XXXXX.COM >
Signed-off-by: Michael Krufky < XXXX@XXXXX.COM >

---
linux/drivers/media/dvb/dvb-core/dvbdev.c | 13 +++++++++++++
1 file changed, 13 insertions(+)

--- linux/drivers/media/dvb/dvb-core/dvbdev.c.orig
+++ linux/drivers/media/dvb/dvb-core/dvbdev.c
@@ -211,6 +211,8 @@
const struct dvb_device *template, void *priv, int type)
{
struct dvb_device *dvbdev;
+ struct file_operations *dvbdevfops;
+
int id;

if (mutex_lock_interruptible(&dvbdev_register_lock))
@@ -230,12 +232,22 @@
return -ENOMEM;
}

+ dvbdevfops = kzalloc(sizeof(struct file_operations), GFP_KERNEL);
+
+ if (!dvbdevfops) {
+ kfree (dvbdev);
+ mutex_unlock(&dvbdev_register_lock);
+ return -ENOMEM;
+ }
+
memcpy(dvbdev, template, sizeof(struct dvb_device));
dvbdev->type = type;
dvbdev->id = id;
dvbdev->adapter = adap;
dvbdev->priv = priv;
+ dvbdev->fops = dvbdevfops;

+ memcpy(dvbdev->fops, template->fops, sizeof(struct file_operations));
dvbdev->fops->owner = adap->module;

list_add_tail (&dvbdev->list_head, &adap->device_list);
@@ -263,6 +275,7 @@
dvbdev->type, dvbdev->id)));

list_del (&dvbdev->list_head);
+ kfree (dvbdev->fops);
kfree (dvbdev);
}
EXPORT_SYMBOL(dvb_unregister_device);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/