Define the main clock frequency in every at91sam9n12 boards.
Remove the old main clock definition.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91sam9n12ek.dts | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts
Define the main clock frequency in every at91sam9x5 boards.
Remove the old main clock definition.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91-ariag25.dts | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/at91-ariag25.dts
b/a
Dmitry,
I didn't see the MSC_TIMESTAMP before. I should have been more up to
date. I've looked at MSC_TIMESTAMP change and the first impression was
that it is something we can live with. After discussing details with
my colleagues here we came to a conclusion that:
a) we do need absolute time.
b)
On 17/07/2013 19:13, Russell King - ARM Linux wrote:
On Wed, Jul 17, 2013 at 05:37:13PM +0200, Boris BREZILLON wrote:
Move at91 clk init from early_init to timer_init for all at91sam9 non dt
boards.
Using black ball point pen, please complete the following sentence using
as many words as you de
Define the main clock frequency in every sama5d3 boards.
Remove the old main clock definition.
Include the appropriate peripheral options according to peripherals
availability.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/sama5d31ek.dts |4
arch/arm/boot/dts/sama5d33ek.dts |
Hi Matthew,
A bug was opened that reports a regression that prevents a system from
booting[0]. After a kernel bisect, it was found that reverting the
following commit resolved this bug:
commit 68d929862e29a8b52a7f2f2f86a0600423b093cd
Author: Matthew Garrett
Date: Sat Mar 2 19:40:17 2013 -0500
Please pull the following nfsd fixes from
git://linux-nfs.org/~bfields/linux.git for-3.11
Just three minor bugfixes.
--b.
Dan Carpenter (1):
svcrdma: underflow issue in decode_write_list()
David Jeffery (1):
lockd:
On Mon, 8 Jul 2013 23:54:55 +0300 Maxim Levitsky
wrote:
> Based partially on MS standard spec quotes from Alex Dubov.
>
> As any code that works with user data this driver isn't
> recommended to use to write cards that contain valuable data.
>
> It tries its best though to avoid data corrupti
On Wed, 2013-07-17 at 16:34 -0400, Joseph Salisbury wrote:
> Hi Matthew,
>
> A bug was opened that reports a regression that prevents a system from
> booting[0]. After a kernel bisect, it was found that reverting the
> following commit resolved this bug:
This should be fixed by f8b8404337de4e246
Here's a set of patches that do two main things:
(1) Provide a general purpose associative array implementation.
(2) Use the associative array implementation to provide key pointer storage
for keyrings thereby massively increasing capacity.
There are numerous smaller patches also that ar
Drop the permissions argument from __keyring_search_one() as the only caller
passes 0 here - which causes all checks to be skipped.
Signed-off-by: David Howells
---
security/keys/internal.h |3 +--
security/keys/key.c |2 +-
security/keys/keyring.c |9 +++--
3 files change
key_is_dead() should take a const key pointer argument as it doesn't modify
what it points to.
Signed-off-by: David Howells
---
security/keys/internal.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/keys/internal.h b/security/keys/internal.h
index df971fe..490a
Define a __key_get() wrapper to use rather than atomic_inc() on the key usage
count as this makes it easier to hook in refcount error debugging.
Signed-off-by: David Howells
---
Documentation/security/keys.txt | 13 -
include/linux/key.h | 10 +++---
security/key
Search functions pass around a bunch of arguments, each of which gets copied
with each call. Introduce a search context structure to hold these.
Whilst we're at it, create a search flag that indicates whether the search
should be directly to the description or whether it should iterate through al
Search for auth-key by name rather than by target key ID as, in a future
patch, we'll by searching directly by index key in preference to iteration
over all keys.
Signed-off-by: David Howells
---
security/keys/request_key_auth.c | 21 +++--
1 file changed, 7 insertions(+), 14
Consolidate the concept of an 'index key' for accessing keys. The index key
is the search term needed to find a key directly - basically the key type and
the key description. We can add to that the description length.
This will be useful when turning a keyring into an associative array rather
th
Make make_key_ref() take a bool possession parameter and make
is_key_possessed() return a bool.
Signed-off-by: David Howells
---
Documentation/security/keys.txt |7 +++
include/linux/key.h |4 ++--
security/keys/keyring.c |5 +++--
3 files changed, 8 insertio
Skip key state checks (invalidation, revocation and expiration) when checking
for possession. Without this, keys that have been marked invalid, revoked
keys and expired keys are not given a possession attribute - which means the
possessor is not granted any possession permits and cannot do anythin
Tim Chen wrote:
> > Therefore, I think possible solutions are either
> >
> > (a) built-in the dependent modules
> >
> > # grep crc /lib/modules/3.11.0-rc1+/modules.dep
> > kernel/drivers/scsi/sd_mod.ko: kernel/lib/crc-t10dif.ko
> > kernel/lib/crc-t10dif.ko:
>
> This approach
On Wed, 2013-07-17 at 21:43 +0100, David Howells wrote:
> Add a generic associative array implementation that can be used as the
> container for keyrings, thereby massively increasing the capacity available
> whilst also speeding up searching in keyrings that contain a lot of keys.
> +extern int a
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
> It's quite common that we need to dynamically change some pins for a
> device for runtime PM, or toggle a pin between rx and tx. Changing all
> the pins for a device is not efficient way of doing it.
>
> So let's allow setting up multiple active state
Joe Perches wrote:
> bool type makes me queasy.
:-)
I've no particular objection to naming it something else - but what? 'Mark'
maybe?
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Lorenzo,
On Tue, Jul 16, 2013 at 05:05:42PM +0100, Lorenzo Pieralisi wrote:
> Hello,
>
> version v5 of VExpress SPC driver, please read on the changelog for major
> changes and explanations.
>
> The probing scheme is unchanged, since after trying the early platform
> devices approach it appea
On Mon, 15 Jul 2013 13:47:51 +0300 "Kirill A. Shutemov"
wrote:
> From: "Kirill A. Shutemov"
>
> Locking head page means locking entire compound page.
> If we try to lock tail page, something went wrong.
>
> ..
>
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -639,6 +639,7 @@ void __lock_page(
Hi Pawel,
On Wed, Jul 17, 2013 at 03:20:11PM +0100, Pawel Moll wrote:
> On Wed, 2013-07-17 at 15:16 +0100, Nicolas Pitre wrote:
> > On Wed, 17 Jul 2013, Pawel Moll wrote:
> >
> > > On Wed, 2013-07-17 at 13:33 +0100, Nicolas Pitre wrote:
> > > > If this is really miscelaneous code that really does
This patch is similar to commit 1762a59d8e8b5e99f6f4a0f292b40f3cacb108ba.
The same non-standard interface descriptor causes snd_usb_create_mixer()
to fail for the Focusrite Scarlett 18i8 as well.
Signed-off-by: Chris J Arges
---
sound/usb/quirks-table.h | 46 +++
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
> To toggle dynamic states, let's add the optional active state in
> addition to the static default state. Then if the optional active
> state is defined, we can require that idle and sleep states cover
> the same pingroups as the active state.
>
> Then
>
> We could extend the symbol option part to retreive values from a binary.
> Something like this:
>
> config FOOBAR
> bool
> option exec="true"
>
> FOOBAR would assume the value "y" if the command true has exit code == 0,
> otherwise "n".
> And similar conversions for other ty
If usb_8dev_start() fails to submit urb,
it unanchors the urb but forgets to free it.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/can/usb/usb_8dev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/can/usb/usb_8
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
> We want to have static pin states handled separately from
> dynamic pin states, so let's add optional state_active.
>
> Then if state_active is defined, let's check and make sure
> state_idle and state_sleep match state_active for the
> pin groups to
On 07/16/2013 03:05 AM, Tony Lindgren wrote:
> To toggle dynamic states, let's add the optional active state in
> addition to the static default state. Then if the optional active
> state is defined, we can require that idle and sleep states cover
> the same pingroups as the active state.
>
> Then
Hi Nicolas,
On Wed, Jul 17, 2013 at 02:29:02PM -0400, Nicolas Pitre wrote:
> On Wed, 17 Jul 2013, Russell King - ARM Linux wrote:
>
> > On Wed, Jul 17, 2013 at 11:57:55AM -0400, Nicolas Pitre wrote:
> > > The sanest location at this point might simply be
> > > drivers/platform/vexpress_spc.c or
On Tue, 16 Jul 2013 13:24:21 -0400 Vivek Goyal wrote:
> Michael, Hatayama, in case this series can't go in 3.11, do you have other
> ideas where a small hack fix will allow kdump to work on s390 and we
> don't have to revert the mmap() patches.
This would certainly be the preferred option at thi
On Mon, 15 Jul 2013 17:26:59 +0200 Maxime Ripard
wrote:
> Sorry to bother you again with the framebuffer stuff but the new
> maintainer doesn't appear to be responsive either.
Jean-Christophe is doing things - on 11 July he sent out a call for
late patches to linux-fb...@vger.kernel.org.
So ho
On Wed 17-07-13 10:52:18, Dave Jones wrote:
> On Wed, Jul 17, 2013 at 02:53:22PM +0200, Jan Kara wrote:
> > On Tue 16-07-13 16:25:33, Dave Jones wrote:
> > > I've seen this happen a few times this week..
> > Thanks for report! Was this when fuzzing or just normal desktop load?
> > What is ino
On Wed, Jul 17, 2013 at 06:00:49PM +0200, Michael Holzheu wrote:
> > On Tue, Jul 16, 2013 at 06:18:10PM +0200, Michael Holzheu wrote:
> > > Hello Andrew,
> > >
> > > Here a new kdump patch series that we have discussed with Vivek and
> > > Hatayama during the last months.
> > >
> > > Besides of the
On Wed, Jul 17, 2013 at 11:38:50PM +0200, Jan Kara wrote:
> > It was running this..
> > https://github.com/kernelslacker/io-tests/blob/master/setup.sh
> > in a loop. After about 6 hours, that fell out. It made it all the way
> > through
> > every test a few times, which is odd, as the test
On Wednesday, July 17, 2013 09:41:08 AM Joe Perches wrote:
> On Wed, 2013-07-17 at 16:30 +, Shuah Khan wrote:
> > On 07/17/2013 10:09 AM, Joe Perches wrote:
> > > On Wed, 2013-07-17 at 09:57 -0600, Shuah Khan wrote:
> > >> A new trace event is added to pm events to print time it takes to
> > >
On Wed, Jul 17, 2013 at 11:16:49PM +0200, Sam Ravnborg wrote:
> +
> +static void exec_command(const char *command, struct symbol *sym)
> +{
> + char buffer[2048];
> + FILE *stream;
Just some indentation level saving:
> +
> + stream = popen(command, "r");
> +
> + if (stream != NULL
CONFIG_ARCH_MEMORY_PROBE enables /sys/devices/system/memory/probe
interface, which allows a given memory address to be hot-added as
follows. (See Documentation/memory-hotplug.txt for more detail.)
# echo start_address_of_new_memory > /sys/devices/system/memory/probe
This probe interface is requir
On Wed, Jul 17, 2013 at 10:14:49AM +0400, James Bottomley wrote:
> On Tue, 2013-07-16 at 14:18 -0700, Paul E. McKenney wrote:
> > On Tue, Jul 16, 2013 at 10:27:09PM +0400, James Bottomley wrote:
> > > On Mon, 2013-07-15 at 15:38 -0700, Linus Torvalds wrote:
> > > > On Mon, Jul 15, 2013 at 3:08 PM,
On 07/08/13 08:35, Stephen Boyd wrote:
> On 06/27, Olof Johansson wrote:
>> On Tue, Jun 25, 2013 at 01:02:12PM -0700, Stephen Boyd wrote:
>>> Olof/Arnd,
>>>
>>> These patches remove the ARM local timer API. The ARM architected
>>> timers have already moved away from this API so this series
>>> migr
On Thu, 2013-07-18 at 05:50 +0900, Tetsuo Handa wrote:
> Tim Chen wrote:
> > > Therefore, I think possible solutions are either
> > >
> > > (a) built-in the dependent modules
> > >
> > > # grep crc /lib/modules/3.11.0-rc1+/modules.dep
> > > kernel/drivers/scsi/sd_mod.ko: kernel/lib/
On 07/12/13 05:10, Stephen Boyd wrote:
> On 07/12, Javi Merino wrote:
>> I agree, we should drop the check. It's annoying in uniprocessors and
>> unlikely to be found in the real world unless your gic entry in the dt
>> is wrong.
>>
> Ok. How about this?
Any comments?
>
> 8<-
> Subject:
On Wed, Jul 17, 2013 at 01:15:40PM -0700, Darren Hart wrote:
> On Fri, 2013-07-12 at 17:58 -0700, Darren Hart wrote:
> > Use the DMI interface rather than manually matching DMI strings.
>
> Greg,
>
> The rest of this series is either being dropped or has moved on to
> netdev. This patch however r
Hi,
I'm trying to test the btrfs and ceph contributions to 3.11, without
testing all of 3.11-rc1 (just yet), so I'm testing with the "next"
branch of Chris Mason's tree (commit cbacd76bb3 from
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git)
merged into the for-linus branch of
On Wed, Jul 17, 2013 at 07:40:43AM -0700, Sarah Sharp wrote:
[ ... ]
>
> The result: 75% of their developers are women. If you give a flying
> fuck about diversity, and want to attract women to your open source
The f word is considered highly offensive in some cultures. Granted its use is
now f
I have to say, the entire boolean type seems strange. I haven't looked at
all the users, but wouldn't it be better to provide some simple helpers
to allow call sites to set and test lsbits, and document the array as
requiring 2-byte alignment of pointers?
Factoring it into two features like this
On Thu, 2013-07-18 at 05:50 +0900, Tetsuo Handa wrote:
> Tim Chen wrote:
> > > Therefore, I think possible solutions are either
> > >
> > > (a) built-in the dependent modules
> > >
> > > # grep crc /lib/modules/3.11.0-rc1+/modules.dep
> > > kernel/drivers/scsi/sd_mod.ko: kernel/lib/
On Wed, Jul 17, 2013 at 11:17:19AM -0400, Eduardo Valentin wrote:
> Hello all,
>
> As you noticed, I am working in a way to represent thermal data
> using device tree [1]. Essentially, this should be a way to say
> what to do with a sensor and how to associate (cooling) actions
> with it.
>
Seems
On Wed, 17 Jul 2013, Samuel Ortiz wrote:
> On Wed, Jul 17, 2013 at 02:29:02PM -0400, Nicolas Pitre wrote:
> > At this point I don't really care about the name. I just want the damn
> > thing merged upstream. But after several iterations to either fit one
> > or another maintainers taste, each
On Wed, Jul 17, 2013 at 07:42:44PM +0100, Al Viro wrote:
> On Wed, Jul 17, 2013 at 06:56:16PM +0100, Stefano Stabellini wrote:
>
> > Abuse is never justified, I hope that's clear for everybody.
>
> Depends on details of your definition of abuse.
>
> > So we are down to the definition of verbal a
Sam, All,
Well, while I was fighting on this on my side... ;-)
On 2013-07-17 23:16 +0200, Sam Ravnborg spake thusly:
> > We could extend the symbol option part to retreive values from a binary.
> > Something like this:
> >
> > config FOOBAR
> > bool
> > option exec="true"
> >
>
On Tue, 16 Jul 2013 18:56:39 -0700 Joe Perches wrote:
> On Tue, 2013-07-16 at 18:48 -0700, Linus Torvalds wrote:
> > On Mon, Jul 15, 2013 at 2:51 PM, Joe Perches wrote:
> > >
> > > If this is acceptable, I'll post 5 or so patches at a time
> > > after/if each block of patches is applied.
> >
>
On Wed, 17 Jul 2013, Stephen Boyd wrote:
> On 07/12/13 05:10, Stephen Boyd wrote:
> > On 07/12, Javi Merino wrote:
> >> I agree, we should drop the check. It's annoying in uniprocessors and
> >> unlikely to be found in the real world unless your gic entry in the dt
> >> is wrong.
And that's a li
On 07/17/13 15:34, Nicolas Pitre wrote:
> On Wed, 17 Jul 2013, Stephen Boyd wrote:
>
>> On 07/12/13 05:10, Stephen Boyd wrote:
>>> On 07/12, Javi Merino wrote:
I agree, we should drop the check. It's annoying in uniprocessors and
unlikely to be found in the real world unless your gic ent
On Wed, 2013-07-17 at 11:51 -0700, Sarah Sharp wrote:
> No, it's actually some of the comments I've received that bother me.
> For example, I would never want to deal with the misogynist troll,
> Lubin, EVER again.
It surprises me to see you calling someone names like that, Sarah. It
seems to be c
On Mon, Jun 17, 2013 at 3:35 AM, Paul Bolle wrote:
> Building dma_v3.o triggers two GCC warnings:
> drivers/dma/ioat/dma_v3.c: In function ‘__ioat3_prep_pq16_lock’:
> drivers/dma/ioat/dma_v3.c:264:11: warning: array subscript is below array
> bounds [-Warray-bounds]
> drivers/dma/ioat
Andrew Morton wrote:
> On Mon, 15 Jul 2013 13:47:51 +0300 "Kirill A. Shutemov"
> wrote:
>
> > From: "Kirill A. Shutemov"
> >
> > Locking head page means locking entire compound page.
> > If we try to lock tail page, something went wrong.
> >
> > ..
> >
> > --- a/mm/filemap.c
> > +++ b/mm/file
On Wed, 17 Jul 2013 20:14:40 +0200 Ingo Molnar wrote:
> 1)
>
> Your notion that conflicts and insults somehow hurt group cooperation is
> wrong. It is a scientific fact that open conflict _helps_ cooperation
> while hidden conflict hurts it.
I don't think anyone is seriously suggesting that
On 07/17/2013 02:09 PM, Andrew Morton wrote:
> lock_page() is a pretty commonly called function, and I assume quite a
> lot of people run with CONFIG_DEBUG_VM=y.
>
> Is the overhead added by this patch really worthwhile?
I always thought of it as a developer-only thing. I don't think any of
the
On Wed, Jul 17, 2013 at 06:22:46PM -0400, Nicolas Pitre wrote:
> On Wed, 17 Jul 2013, Samuel Ortiz wrote:
>
> > On Wed, Jul 17, 2013 at 02:29:02PM -0400, Nicolas Pitre wrote:
> > > At this point I don't really care about the name. I just want the damn
> > > thing merged upstream. But after seve
This is the start of the review cycle for the Linux 3.8.13.5 stable kernel.
This version contains 145 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=linux-3.8.y-review;a
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konrad Rzeszutek Wilk
commit 098b1aeaf4d6149953b8f1f8d55c21d85536fbff upstream.
There are two tool-stack that can instruct the Xen PCI frontend
and backend to change states: 'xm' (Python
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiang Liu
commit 6030ea9b35971a4200062f010341ab832e878ac9 upstream.
Memory for zram->disk object may have already been freed after returning
from destroy_device(zram), then it's unsafe f
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Olsa
commit 06f417968beac6e6b614e17b37d347aa6a6b1d30 upstream.
The '!ctx->is_active' check has a valid scenario, so
there's no need for the warning.
The reason is that there's a ti
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: UCHINO Satoshi
commit d68c277b501889b3a50c179d1c3d704db7947b83 upstream.
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joachim Eastwood
commit e39506b466edcda2a7e9d0174d7987ae654137b7 upstream.
Commit 80af9e6d (pcmcia at91_cf: fix raw gpio number usage) forgot
to change the parameter in gpio_get_value af
On 07/17/13 15:02, Guenter Roeck wrote:
> On Wed, Jul 17, 2013 at 07:40:43AM -0700, Sarah Sharp wrote:
>
> [ ... ]
>>
>> The result: 75% of their developers are women. If you give a flying
>> fuck about diversity, and want to attract women to your open source
>
> The f word is considered highly
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Zach Bobroff
commit d3768d885c6ccbf8a137276843177d76c49033a7 upstream.
ExitBootServices is absolutely supposed to return a failure if any
ExitBootServices event handler changes the memor
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Richard Weinberger
commit 8c58bf3eec3b8fc8162fe557e9361891c20758f2 upstream.
Using this parameter one can disable the storage_size/2 check if
he is really sure that the UEFI does sane gc
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Matt Fleming
commit a6e4d5a03e9e3587e88aba687d8f225f4f04c792 upstream.
commit 3668011d4ad556224f7c012c1e870a6eaa0e59da upstream.
Let's not burden ia64 with checks in the common efivars c
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Slaby
commit 9d66b568a215fe2da2a9db736ebf9b8d66082d88 upstream.
When rtsx_pci_acquire_irq fails in rtsx_pci_probe, we forget to
disable an MSI (if we enabled it). This results in th
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?J=C3=B6rn=20Engel?=
commit 0fbfc46fb0b2f543a8b539e94c6c293ebc0b05a6 upstream.
This patch fixes a potential buffer overflow while processing
iscsi_node_auth input for configfs a
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Hutchings
commit b8cb62f82103083a6e8fa5470bfe634a2c06514d upstream.
1. Check for allocation failure
2. Clear the buffer contents, as they may actually be written to flash
3. Don't le
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hannes Reinecke
commit 6c182cd88d179cbbd06f4f8a8a19b6977940753f upstream.
When multipath needs to retry an ioctl the reference to the
current live table needs to be dropped. Otherwise a
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka
commit b1bf2de07271932326af847a3c6a01fdfd29d4be upstream.
Fix a boundary condition that caused failure for certain device sizes.
The problem is reported at
http://code
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit 058ebd0eba3aff16b144eabf4510ed9510e1416e upstream.
Jiri managed to trigger this warning:
[] ==
[] [ INFO: pos
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helge Deller
commit 5b879d78bc0818aa710f5d4d9abbfc2aca075cc3 upstream.
When running the LTP testsuite one may hit this kernel BUG() with the
write06 testcase:
kernel BUG at mm/filemap.c
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mika Westerberg
commit 10a0b6176b9f8b026ce07acd8f755297653c443c upstream.
There are few places in power.c where debug messages have no newline
at the end. Reading such debug messages fr
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Satoru Takeuchi
commit 6b59e366e074d3962e04f01efb8acc10a33c0e1e upstream.
The check, "IS_ENABLED(CONFIG_X86_64) != efi_enabled(EFI_64BIT)",
in setup_arch() can be replaced by efi_is_enab
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Richard Weinberger
commit f8b8404337de4e2466e2e1139ea68b1f8295974f upstream.
This patch reworks the UEFI anti-bricking code, including an effective
reversion of cc5a080c and 31ff2f20. It
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Emmanuel Grumbach
commit 8a487b1a7432b20ff3f82387a8ce7555a964b44e upstream.
When the queue is unmapped while it was so loaded that
mac80211's was stopped, we need to wake the queue after
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wanpeng Li
commit cea27eb2a202959783f81254c48c250ddd80e129 upstream.
The logic for the memory-remove code fails to correctly account the
Total High Memory when a memory block which conta
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Gabor Juhos
commit 0a6f3a8ebaf13407523c2c7d575b4ca2debd23ba upstream.
The current code uses the same index value both
for the channel information array and for the TX
power table. The in
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sujith Manoharan
commit 30d5b709da23f4ab9836c7f66d2d2e780a69cf12 upstream.
For AR9485 boards with XLNA, the default gpio config
is not set correctly, fix this.
Signed-off-by: Sujith Man
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Williamson
commit 60d0ca3cfd199b6612f4999a3470dad38bb1 upstream.
If we use a large mapping, the expectation is that only unmaps from
the first pte in the superpage are supported
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Pablo Neira Ayuso
commit bc6bcb59dd7c184d229f9e86d08aa56059938a4c upstream.
This target assumes that tcph->doff is well-formed, that may be well
not the case. Add extra sanity checkings
On Wed, Jul 17, 2013 at 09:03:35AM -0400, Steven Rostedt wrote:
> On Wed, 2013-07-17 at 13:30 +0100, Ricardo Ferreira wrote:
> > Slashdot is just a cesspool of trolls, not a good comparison.
>
> Point taken.
>
> I posted this privately, and I think I'll repost it here. I need to
> modify it a bit
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: "zhangwei(Jovi)"
commit fa44063f9ef163c3a4c8d8c0465bb8a056b42035 upstream.
When wrong argument is passed into uprobe_events it does not return
an error:
[root@jovi tracing]# echo 'p:myp
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Phil Oester
commit 70d19f805f8c047fc0a28dec9306b3773971c8d9 upstream.
As a followup to commit 409b545a ("netfilter: xt_TCPMSS: Fix violation
of RFC879 in absence of MSS option"), John He
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jan Kara
commit 8af8eecc1331dbf5e8c662022272cf667e213da5 upstream.
The arithmetics adding delalloc blocks to the number of used blocks in
ext4_getattr() can easily overflow on 32-bit arc
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Junxiao Bi
commit ef962df057aaafd714f5c22ba3de1be459571fdf upstream.
Inlined xattr shared free space of inode block with inlined data or data
extent record, so the size of the later two
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Darren Hart
commit 29692d05647cb7ecea56242241f77291d5624b95 upstream.
Use DMI_BOARD_NAME to determine if we are running on a MinnowBoard and
set the uart clock to 50MHz if so. This remov
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Artem Bityutskiy
commit 605c912bb843c024b1ed173dc427cd5c08e5d54d upstream.
Al Viro pointed me to the fact that '->readdir()' and '->llseek()' have no
mutual exclusion, which means the 'u
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Theodore Ts'o
commit fe52d17cdd343ac43c85cf72940a58865b9d3bfb upstream.
Some of the functions which modify the jbd2 superblock were not
updating the checksum before calling jbd2_write_su
3.8.13.5 -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 wor
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Laszlo Ersek
commit 0b0c002c340e78173789f8afaa508070d838cf3d upstream.
... because the "clock_event_device framework" already accounts for idle
time through the "event_handler" function
3.8.13.5 -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
3.8.13.5 -stable review patch. If anyone has any objections, please let me
know.
--
From: Maarten ter Huurne
commit 6ca792edc13c409e8d4eb9001e048264c6a2eb64 upstream.
Subtracting the number of the first data block places the superblock
backups one block too early, corrupting
601 - 700 of 982 matches
Mail list logo
