From: Rafael J. Wysocki
If the slot unique number is passed as an additional argument to
acpiphp_register_hotplug_slot(), the slot field in struct
acpiphp_slot is not necessary and may be dropped, so make that
happen.
Signed-off-by: Rafael J. Wysocki
---
drivers/pci/hotplug/acpiphp.h |
From: Rafael J. Wysocki
To make the code in register_slot() a bit easier to follow, change
the way the slot allocation part is organized. Drop one local
variable that's not used any more after that modification.
This code change should not lead to any changes in behavior.
Signed-off-by:
From: Rafael J. Wysocki
Modify handle_hotplug_event() to pass the entire context object
(instead of its fields individually) to work functions started by it.
This change makes the subsequent consolidation of the event handling
work functions a bit more straightforward.
Signed-off-by: Rafael J.
From: Rafael J. Wysocki
Subject:
Using the hotplug context objects introduced previously rework the
ACPI-based PCI hotplug (ACPIPHP) core code to get to acpiphp_bridge
objects associated with hotplug bridges from those context objects
rather than from the global list of hotplug bridges.
From: Rafael J. Wysocki
There are separate handling event functions for hotplug bridges and
for hotplug functions, but they may be combined into one common
hotplug event handling function which simplifies the code slightly.
That also allows a theoretical bug to be dealt with which in
principle
From: Rafael J. Wysocki
When either a new hotplug bridge or a new hotplug function is added
by the ACPI-based PCI hotplug (ACPIPHP) code, attach a context object
to its ACPI handle to store hotplug-related information in it. To
start with, put the handle's bridge and function pointers into that
On Thursday, July 11, 2013 5:55 PM, Kishon Vijay Abraham I wrote:
> On Thursday 11 July 2013 11:19 AM, Jingoo Han wrote:
> > Exynos PCIe IP consists of Synopsys specific part and Exynos
> > specific part. Only core block is a Synopsys designware part;
> > other parts are Exynos specific.
> > Also,
From: Rafael J. Wysocki
Using the hotplug context objects introduced previously rework the
ACPI-based PCI hotplug (ACPIPHP) core code so that all notifications
for ACPI device objects corresponding to the hotplug PCI devices are
handled by one function, handle_hotplug_event(), which recognizes
From: Rafael J. Wysocki
When a new ACPIPHP function is added by register_slot() and the
notify handler cannot be installed for it, register_slot() returns an
error status without cleaning up, which causes the entire namespace
walk in acpiphp_enumerate_slots() to be aborted, although it still
may
From: Rafael J. Wysocki
Since acpi_pci_slot_enumerate() and acpiphp_enumerate_slots() can get
the ACPI device handle they need from bus->bridge, it is not
necessary to pass that handle to them as an argument.
Drop the second argument of acpi_pci_slot_enumerate() and
acpiphp_enumerate_slots(),
From: Rafael J. Wysocki
The acpiphp_enumerate_slots() function is now split into two parts,
acpiphp_enumerate_slots() proper and init_bridge_misc() which is
only called by the former. If these functions are combined,
it is possible to make the code easier to follow and to clean up
the error
From: Rafael J. Wysocki
Two checks in check_hotplug_bridge() are redundant (they have been
done by the caller already), so drop them.
Signed-off-by: Rafael J. Wysocki
---
drivers/pci/hotplug/acpiphp_glue.c |6 --
1 file changed, 6 deletions(-)
Index:
From: Rafael J. Wysocki
Rework register_slot() to create a struct acpiphp_func object for
every function it is called for and to create acpiphp slots for all
of them. Although acpiphp_register_hotplug_slot() is only called for
the slots whose functions are identified as "ejectable", so that
Hi,
I've made some progress with my ACPIPHP rework since I posted the series last
time and here goes an update.
First off, the previous series was somewhat racy, which should be fixed now.
Apart from this there's quite some new material on top of the patches I posted
last time (or rather on top
From: Mika Westerberg
Both acpiphp_disable_slot() and acpiphp_eject_slot() are always
called together so instead of calling each separately we can
consolidate them into one function acpiphp_disable_and_eject_slot()
that does both (but it will return success on _EJ0 failures that
were ignored in
On Thu, Jul 11, 2013 at 5:50 AM, Jason Cooper wrote:
> On Wed, Jul 10, 2013 at 10:08:50PM +0800, Haojian Zhuang wrote:
>> On Wed, Jul 10, 2013 at 8:24 PM, Jason Cooper wrote:
>> > On Wed, Jul 10, 2013 at 04:19:46PM +0800, Haojian Zhuang wrote:
>> >> On Tue, Jul 9, 2013 at 8:49 PM, Jason Cooper
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
tags/rdma-for-linus
Main (updated) batch of InfiniBand/RDMA changes for 3.11 merge window:
- AF_IB (native IB addressing) for
On 07/12/2013 12:47 AM, Steven Rostedt wrote:
> On Thu, 2013-07-11 at 08:31 +0800, Chen Gang wrote:
>> Like other trace_selftest_startup_*, trace_selftest_startup_function()
>> and trace_selftest_startup_function_graph() need in normal section, or
>> may cause section mismatch.
>>
>> The related
On Thu, Jul 11, 2013 at 7:23 PM, Neil Zhang wrote:
> Haojian,
>
>
>> -Original Message-
>> From: Haojian Zhuang [mailto:haojian.zhu...@gmail.com]
>> Sent: 2013年7月10日 13:59
>> To: Arnd Bergmann
>> Cc: Thomas Petazzoni; Neil Zhang; Grant Likely;
>> devicetree-disc...@lists.ozlabs.org;
On 07/10/2013 11:01 AM, Chen Gang F T wrote:
>
>> > Hmm..., do we need call kobject_get() before kobject_put() in failure
>> > processing block ?
>> >
> Oh, sorry for what I said for kobject_get/put() items above, it is
> incorrect.
>
> What about the diff below for kobject_get() ?
>
>
Convert drivers/pnp/driver.c bus legacy pm_ops to dev_pm_ops using
existing suspend and resume routines. Added freeze interface to
handle PM_EVENT_FREEZE correctly with dev_pm_ops. pm_op() looks for
freeze interface when the event is PM_EVENT_FREEZE.
Signed-off-by: Shuah Khan
---
On Friday, July 12, 2013 12:41 AM, Thierry Reding wrote:
> On Thu, Jul 11, 2013 at 02:49:43PM +0900, Jingoo Han wrote:
> [...]
> > diff --git a/drivers/pci/host/Makefile b/drivers/pci/host/Makefile
> [...]
> > obj-$(CONFIG_PCI_MVEBU) += pci-mvebu.o
> > obj-$(CONFIG_PCIE_DW) += pcie-designware.o
On 07/11/2013 04:08 PM, Dave Jones wrote:
> +static int sys_get_curr_temp(struct thermal_zone_device *tzd, unsigned
long *temp)
> +static int sys_get_trip_temp(struct thermal_zone_device *tzd,
> +int sys_set_trip_temp(struct thermal_zone_device *tzd, int trip,
> +static int
On Thu, Jul 11, 2013 at 3:39 AM, Jean Delvare wrote:
> On Thu, 11 Jul 2013 16:53:43 +1000, Stephen Rothwell wrote:
>> On Thu, 11 Jul 2013 07:57:00 +0200 Jean Delvare wrote:
>> > On Thu, 11 Jul 2013 10:27:24 +1000, Stephen Rothwell wrote:
>> > > Why have you just rebased the jdelvare-hwmon series
> +static int sys_get_curr_temp(struct thermal_zone_device *tzd, unsigned long
> *temp)
> +static int sys_get_trip_temp(struct thermal_zone_device *tzd,
> +int sys_set_trip_temp(struct thermal_zone_device *tzd, int trip,
> +static int sys_get_trip_type(struct thermal_zone_device *thermal,
On Thu, 2013-07-11 at 22:26 +0200, Jiri Kosina wrote:
> Introduce a method for run-time instrucntion patching on a live SMP kernel
Some of the typos anyway.
s/instrunction/instruction
[]
> v2 -> v3:
> + fixed few typos (Joe Perches)
[]
> + /* we are not interested in non-int3 faults
Ben,
Why do I have 21 patches from you marked for -stable trees in the
3.11-rc1 merge window, like the one quoted below? All of these look
serious enough that they should have gone into the 3.10-rc releases,
especially as the date of when they were submitted gave you plenty of
time to get them
On Thu, 2013-07-11 at 12:26 +0200, Alexander Gordeev wrote:
> On Wed, May 22, 2013 at 07:03:05PM +0200, Jens Axboe wrote:
> > On Wed, May 22 2013, Alexander Gordeev wrote:
> > > On Wed, May 22, 2013 at 08:50:03AM +0900, Tejun Heo wrote:
> > > > Hmm. I'd normally apply this patch but block
On Thu, 11 Jul 2013, Andrew Morton wrote:
> > PTR_ERR() may not imply IS_ERR(),
>
> Well why not. Are we saying that code can legitimately convert the
> PTR_ERR() return value back into a pointer? If so that sounds nuts.
>
ERR_PTR() is just delivering a payload that can be interpreted by
On Thu, 11 Jul 2013, Benjamin Tissoires wrote:
> The USB hid implementation does retrieve the reports during the start.
> However, this implementation does not call the HID command GET_REPORT
> (which would fetch the current status of each report), but use the
> DATA command, which is an Output
On Thu, 11 Jul 2013, Benjamin Tissoires wrote:
> We can re-enable hidinput_input_event to allow the leds of bluetooth
> keyboards to be set.
> Now the callbacks uses hid core to retrieve the right HID report to
> send, so this version is safer.
>
> Signed-off-by: Benjamin Tissoires
Acked-by:
From: Stephen Warren
Architectures should fully validate whether kexec is possible as part of
machine_kexec_prepare(), so that user-space's kexec_load() operation can
report any problems. Performing validation in machine_kexec() itself is
too late, since it is not allowed to return.
Prior to
On Thu, Jul 11, 2013 at 06:29:35PM -0400, Dave Jones wrote:
> On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote:
> >
> > I'm sitting on top of over 170 more patches that have been marked for
> > the stable releases right now that are not included in this set of
> >
Hey guys,
according the dw_apb_timer I need your statement...
Am 06.07.2013 23:00, schrieb Thomas Gleixner:
> Ulrich,
>
> On Sat, 6 Jul 2013, Ulrich Prinz wrote:
>
>> I got the message. With modifying the existing driver to support more
>> function pointers in its system struct and assigning
* Guenter Roeck (li...@roeck-us.net) wrote:
> On Thu, Jul 11, 2013 at 12:00:54PM -0700, Chris Wright wrote:
> > * Guenter Roeck (li...@roeck-us.net) wrote:
> > > On Tue, Jul 09, 2013 at 04:22:52PM -0700, Chris Wright wrote:
> > > > One thing I've seen is the BIOS zeroing the base register address
On Thu, 11 Jul 2013 15:27:46 -0700 (PDT) David Rientjes
wrote:
> On Thu, 11 Jul 2013, Andrew Morton wrote:
>
> > On Thu, 11 Jul 2013 15:13:03 -0700 (PDT) David Rientjes
> > wrote:
> >
> > > > +int vma_dup_policy(struct vm_area_struct *src, struct vm_area_struct
> > > > *dst)
> > > > +{
> >
From: "Kirill A. Shutemov"
Software Developer’s Manual covers two more TLB configurations:
63H Data TLB: 1 GByte pages, 4-way set associative, 4 entries
76H Instruction TLB: 2M/4M pages, fully associative, 8 entries
Let's detect them as well.
Signed-off-by: Kirill A. Shutemov
Acked-by: Alex
On Thu, 11 Jul 2013, H. Peter Anvin wrote:
> > synchronization after replacing "all but first" instructions should not
> > be necessary (on Intel hardware), as the syncing after the subsequent
> > patching of the first byte provides enough safety.
> > But there's not only Intel HW out there, and
Separate out the allocation of the cpufreq policy structure (along with
its error handling) to a helper function. This makes the code easier to
read and also helps with some upcoming code reorganization.
Signed-off-by: Srivatsa S. Bhat
---
drivers/cpufreq/cpufreq.c | 50
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Jul 13 22:11:24 UTC 2013.
Anything
On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote:
>
> I'm sitting on top of over 170 more patches that have been marked for
> the stable releases right now that are not included in this set of
> releases. The fact that there are this many patches for stable stuff
>
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 3594f4c0d7bc51e3a7e6d73c44e368ae079e42f3 upstream.
The exposed interface for cm_notify_event() could result in the event msg
string being parsed as a format string. Make sure
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit ffc8b30866879ed9ba62bd0a86fecdbd51cd3d19 upstream.
Disk names may contain arbitrary strings, so they must not be
interpreted as format strings. It seems that only md allows
On Thu, 11 Jul 2013, Andrew Morton wrote:
> On Thu, 11 Jul 2013 15:13:03 -0700 (PDT) David Rientjes
> wrote:
>
> > > +int vma_dup_policy(struct vm_area_struct *src, struct vm_area_struct
> > > *dst)
> > > +{
> > > + struct mempolicy *pol = mpol_dup(vma_policy(src));
> > > +
> > > + if
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 1c8fca1d92e14859159a82b8a380d220139b7344 upstream.
The template lookup interface does not provide a way to use format
strings, so make sure that the interface cannot be abused
On 07/12/2013 04:03 AM, Rafael J. Wysocki wrote:
> On Friday, July 12, 2013 03:45:17 AM Srivatsa S. Bhat wrote:
>>
>> Hi,
>
> Hi,
>
>> Commit a66b2e (cpufreq: Preserve sysfs files across suspend/resume) caused
>> some subtle regressions in the cpufreq subsystem during suspend/resume.
>> This
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 7b175c46720f8e6b92801bb634c93d1016f80c62 upstream.
This hopefully will help point developers to the proper way that patches
should be submitted for inclusion in the
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jonathan Salwan
commit 542db01579fbb7ea7d1f7bb9ddcef1559df660b2 upstream.
In drivers/cdrom/cdrom.c mmc_ioctl_cdrom_read_data() allocates a memory
area with kmalloc in line 2885.
2885
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit a1dc1937337a93e699eaa56968b7de6e1a9e77cf upstream.
[ 1121.231883] BUG: sleeping function called from invalid context at
kernel/rwsem.c:20
[ 1121.231935] in_atomic(): 1,
-Original Message-
From: Srivatsa S. Bhat [mailto:srivatsa.b...@linux.vnet.ibm.com]
Sent: Friday, July 12, 2013 00:15
> Robert, Durgadoss, it would be great if you could try it out and
> see if it works well for your usecase. I tested it locally and
> cpufreq related files did retain
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 828c6a102b1f2b8583fadc0e779c46b31d448f0b upstream.
This reverts commit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366.
As reported by Stefan, this device already works
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Zhang Yi
commit 13d60f4b6ab5b702dc8d2ee20999f98a93728aec upstream.
The futex_keys of process shared futexes are generated from the page
offset, the mapping host and the mapping index of the
cpufreq_add_dev_interface() includes the work of exposing the interface
to the device, as well as a lot of unrelated stuff. Move the latter to
cpufreq_add_dev(), where it is more appropriate.
Signed-off-by: Srivatsa S. Bhat
---
drivers/cpufreq/cpufreq.c | 43
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit 247500820ebd02ad87525db5d9b199e5b66f6636 upstream.
A freebsd NFSv4.0 client was getting rare IO errors expanding a tarball.
A network trace showed the server returning
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 2ee3e26c673e75c05ef8b914f54fadee3d7b9c88 upstream.
Commit 39c60a0948cc '[SCSI] sd: fix array cache flushing bug causing
performance problems' added temp as a pointer to
On Friday, July 12, 2013 03:45:17 AM Srivatsa S. Bhat wrote:
>
> Hi,
Hi,
> Commit a66b2e (cpufreq: Preserve sysfs files across suspend/resume) caused
> some subtle regressions in the cpufreq subsystem during suspend/resume.
> This patchset is aimed at rectifying those problems, by fixing the
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Gleb Natapov
commit 03617c188f41eeeb4223c919ee7e66e5a114f2c6 upstream.
Some userspaces do not preserve unusable property. Since usable
segment has to be present according to VMX spec we can
On Thu, 11 Jul 2013 15:13:03 -0700 (PDT) David Rientjes
wrote:
> > +int vma_dup_policy(struct vm_area_struct *src, struct vm_area_struct *dst)
> > +{
> > + struct mempolicy *pol = mpol_dup(vma_policy(src));
> > +
> > + if (IS_ERR(pol))
> > + return PTR_ERR(pol);
>
> PTR_ERR()
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 1c8fca1d92e14859159a82b8a380d220139b7344 upstream.
The template lookup interface does not provide a way to use format
strings, so make sure that the interface cannot be abused
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 3ebacb05044f82c5f0bb456a894eb9dc57d0ed90 upstream.
The test if bitmap access is out of bound could errorneously pass if the
device size is divisible by 16384 sectors and
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 3ebacb05044f82c5f0bb456a894eb9dc57d0ed90 upstream.
The test if bitmap access is out of bound could errorneously pass if the
device size is divisible by 16384 sectors and
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 7b175c46720f8e6b92801bb634c93d1016f80c62 upstream.
This hopefully will help point developers to the proper way that patches
should be submitted for inclusion in the
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit 247500820ebd02ad87525db5d9b199e5b66f6636 upstream.
A freebsd NFSv4.0 client was getting rare IO errors expanding a tarball.
A network trace showed the server returning
Now that we have the infrastructure to perform a light-weight init/tear-down,
use that in the cpufreq CPU hotplug notifier when invoked from the
suspend/resume path.
This also ensures that the file permissions of the cpufreq sysfs files are
preserved across suspend/resume, something which commit
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
commit 2cb33cac622afde897aa02d3dcd9fbba8bae839e upstream.
A malicious monitor can craft an auth reply message that could cause a
NULL function pointer dereference in the client's
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 2ee3e26c673e75c05ef8b914f54fadee3d7b9c88 upstream.
Commit 39c60a0948cc '[SCSI] sd: fix array cache flushing bug causing
performance problems' added temp as a pointer to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jonathan Salwan
commit 542db01579fbb7ea7d1f7bb9ddcef1559df660b2 upstream.
In drivers/cdrom/cdrom.c mmc_ioctl_cdrom_read_data() allocates a memory
area with kmalloc in line 2885.
2885
During suspend/resume we would like to do a light-weight init/teardown of
CPUs in the cpufreq subsystem and preserve certain things such as sysfs files
etc across suspend/resume transitions. Add a flag called 'frozen' to help
distinguish the full init/teardown sequence from the light-weight one.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit ffc8b30866879ed9ba62bd0a86fecdbd51cd3d19 upstream.
Disk names may contain arbitrary strings, so they must not be
interpreted as format strings. It seems that only md allows
During cpu offline, when the policy->cpu is going down, some other CPU
present in the policy->cpus mask is nominated as the new policy->cpu.
Extract this functionality from __cpufreq_remove_dev() and implement
it in a helper function. This helps in upcoming code reorganization.
Signed-off-by:
To perform light-weight cpu-init and teardown in the cpufreq subsystem
during suspend/resume, we need to separate out the 2 main functionalities
of the cpufreq CPU hotplug callbacks, as outlined below:
1. Init/tear-down of core cpufreq and CPU-specific components, which are
critical to the
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Jul 13 22:18:05 UTC 2013.
Anything
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Rusty Russell
commit 8d8022e8aba85192e937f1f0f7450e256d66ae5c upstream.
v3.8-rc1-5-g1fb9341 was supposed to stop parallel kvm loads exhausting
percpu memory on large machines:
Now we have
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
commit 2cb33cac622afde897aa02d3dcd9fbba8bae839e upstream.
A malicious monitor can craft an auth reply message that could cause a
NULL function pointer dereference in the client's
3.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Hocko
commit fa460c2d37870e0a6f94c70e8b76d05ca11b6db0 upstream.
This reverts commit e4715f01be697a.
mem_cgroup_put is hierarchy aware so mem_cgroup_put(memcg) already drops
an
The call to cpufreq_update_policy() is placed in the CPU hotplug callback
of cpufreq_stats, which has a higher priority than the CPU hotplug callback
of cpufreq-core. As a result, during CPU_ONLINE/CPU_ONLINE_FROZEN, we end up
calling cpufreq_update_policy() *before* calling cpufreq_add_dev() !
commit a66b2e (cpufreq: Preserve sysfs files across suspend/resume) has
unfortunately caused several things in the cpufreq subsystem to break subtly
after a suspend/resume cycle.
The intention of that patch was to retain the file permissions of the
cpufreq related sysfs files across
Hi,
Commit a66b2e (cpufreq: Preserve sysfs files across suspend/resume) caused
some subtle regressions in the cpufreq subsystem during suspend/resume.
This patchset is aimed at rectifying those problems, by fixing the regression
as well as achieving the original goal of that commit in a proper
On 07/11/2013 04:09 PM, Bjorn Helgaas wrote:
On Thu, Jul 11, 2013 at 3:51 AM, Don Dutile wrote:
On 07/11/2013 05:43 AM, Yijing Wang wrote:
Introduce PCIe Ext Capability Device Serial Number support,
so we can use the unique device serial number to identify
the physical device. During system
On Thu, 11 Jul 2013, Vladimir Cernov wrote:
> This fixes following errors:
> - ERROR: "(foo*)" should be "(foo *)"
> - ERROR: "foo ** bar" should be "foo **bar"
>
> Signed-off-by: Vladimir Cernov
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line "unsubscribe
On Thu, Jul 11, 2013 at 6:01 PM, Greg Kroah-Hartman
wrote:
>
> I'm sitting on top of over 170 more patches that have been marked for
> the stable releases right now that are not included in this set of
> releases. The fact that there are this many patches for stable stuff
> that are
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Jul 13 22:04:03 UTC 2013.
Anything
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 3ebacb05044f82c5f0bb456a894eb9dc57d0ed90 upstream.
The test if bitmap access is out of bound could errorneously pass if the
device size is divisible by 16384 sectors and
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 1c8fca1d92e14859159a82b8a380d220139b7344 upstream.
The template lookup interface does not provide a way to use format
strings, so make sure that the interface cannot be abused
On Wed, 10 Jul 2013, Oleg Nesterov wrote:
> Simple cleanup. Every user of vma_set_policy() does the same work,
> this looks a bit annoying imho. And the new trivial helper which
> does mpol_dup() + vma_set_policy() to simplify the callers.
>
Good idea, just a few simple issues to fix.
> diff
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 7b175c46720f8e6b92801bb634c93d1016f80c62 upstream.
This hopefully will help point developers to the proper way that patches
should be submitted for inclusion in the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
commit 828c6a102b1f2b8583fadc0e779c46b31d448f0b upstream.
This reverts commit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366.
As reported by Stefan, this device already works
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 3594f4c0d7bc51e3a7e6d73c44e368ae079e42f3 upstream.
The exposed interface for cm_notify_event() could result in the event msg
string being parsed as a format string. Make sure
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jonathan Salwan
commit 542db01579fbb7ea7d1f7bb9ddcef1559df660b2 upstream.
In drivers/cdrom/cdrom.c mmc_ioctl_cdrom_read_data() allocates a memory
area with kmalloc in line 2885.
2885
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit 48f0f14ffb6ff4852922994d11fbda418d40100e which was
commit 749c8814f08f12baa4a9c2812a7c6ede7d69507d upstream.
It seems to be misapplied, and not needed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 2ee3e26c673e75c05ef8b914f54fadee3d7b9c88 upstream.
Commit 39c60a0948cc '[SCSI] sd: fix array cache flushing bug causing
performance problems' added temp as a pointer to
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "J. Bruce Fields"
commit 247500820ebd02ad87525db5d9b199e5b66f6636 upstream.
A freebsd NFSv4.0 client was getting rare IO errors expanding a tarball.
A network trace showed the server returning
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
commit 2cb33cac622afde897aa02d3dcd9fbba8bae839e upstream.
A malicious monitor can craft an auth reply message that could cause a
NULL function pointer dereference in the client's
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit ffc8b30866879ed9ba62bd0a86fecdbd51cd3d19 upstream.
Disk names may contain arbitrary strings, so they must not be
interpreted as format strings. It seems that only md allows
On Mon, Apr 22, 2013 at 11:49 AM, Heinrich Schuchardt
wrote:
>
> Hello Justin,
>
> I downloaded the example,
> http://www.lanedo.com/~aleksander/fanotify/fanotify-example.c
> compiled it without modification
> $ gcc fanotify-example.c -o fanotify-example
> and started the executable. In a
I'm sitting on top of over 170 more patches that have been marked for
the stable releases right now that are not included in this set of
releases. The fact that there are this many patches for stable stuff
that are waiting to be merged through the main -rc1 merge window cycle
is
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit a1dc1937337a93e699eaa56968b7de6e1a9e77cf upstream.
[ 1121.231883] BUG: sleeping function called from invalid context at
kernel/rwsem.c:20
[ 1121.231935] in_atomic(): 1,
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 3594f4c0d7bc51e3a7e6d73c44e368ae079e42f3 upstream.
The exposed interface for cm_notify_event() could result in the event msg
string being parsed as a format string. Make sure
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Tyler Hicks
commit 2cb33cac622afde897aa02d3dcd9fbba8bae839e upstream.
A malicious monitor can craft an auth reply message that could cause a
NULL function pointer dereference in the client's
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 3ebacb05044f82c5f0bb456a894eb9dc57d0ed90 upstream.
The test if bitmap access is out of bound could errorneously pass if the
device size is divisible by 16384 sectors
101 - 200 of 1458 matches
Mail list logo
