3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 2856cc2e4d0852c3ddaae9dcb19cb9396512eb08 ]
On a 2-node machine with 256GB of ram we get 512 lines of
console output, which is just too much.
This mimicks Y
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 08280e6c4c2e8049ac61d9e8e3536ec1df629c0d ]
If the MM is not active, only report the top-level PC. Do not try to
access the address space.
Signed-off-by: D
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
[ Upstream commit 55c2770e413e96871147b9406a9c41fe9bc5209c ]
we want syscall_trace_leave() called on exit from any syscall;
skipping its call in case we'd done force_successful_syscall
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daisuke Nishimura
commit 1f5320d5972aa50d3e8d2b227b636b370e608359 upstream.
notify_on_release must be triggered when the last process in a cgroup is
move to another. But if the first(and only)
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 4b35f1c52943851b310afb09047bfe991ac8f5ae upstream.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
drivers/usb/serial/option.c | 16
1 f
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Boullis
commit 301a29da6e891e7eb95c843af0ecdbe86d01f723 upstream.
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
Signed-off
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "Alexis R. Cortes"
commit 470809741a28c3092279f4e1f3f432e534d46068 upstream.
This minor change adds a new system to which the "Fix Compliance Mode
on SN65LVPE502CP Hardware" patch has to be app
Add support for debug_dma_mapping_error() call to avoid warning from
debug_dma_unmap() interface when it checks for mapping error checked
status. Without this patch, device driver failed to check map error
warning is generated.
Signed-off-by: Shuah Khan
---
arch/sparc/include/asm/dma-mapping.h |
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hiro Sugawara
commit d0078e72314df2e5ede03f2102cddde06767c374 upstream.
Fix a deadly typo in macro definition.
Signed-off-by: Hiro Sugawara
Signed-off-by: Hiroshi Doyu
Signed-off-by: Joerg R
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit 9bb71308b8133d643648776243e4d5599b1c193d upstream.
This reverts commit 7e381b0eb1e1a9805c37335562e8dc02e7d7848c.
The commit incorrectly assumed that fork path always performed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pritesh Raithatha
commit a03690e44468dcd3088f6600ab036d17bd2130ff upstream.
Signed-off-by: Pritesh Raithatha
Acked-by: Stephen Warren
Tested-by: Stephen Warren
Signed-off-by: Linus Walleij
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit d87838321124061f6c935069d97f37010fa417e6 upstream.
This reverts commit 7e3aa30ac8c904a706518b725c451bb486daaae9.
The commit incorrectly assumed that fork path always performed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Hocko
commit 7386cdbf2f57ea8cff3c9fde93f206e58b9fe13f upstream.
Git commit 09a1d34f8535ecf9 "nohz: Make idle/iowait counter update
conditional" introduced a bug in regard to cpu hotplug.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream.
The min/max call needed to have explicit types on some architectures
(e.g. mn10300). Use clamp_t instead to avoid the warning
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 2702b1526c7278c4d65d78de209a465d4de2885e upstream.
Calling uname() with the UNAME26 personality set allows a leak of kernel
stack contents. This fixes it by defensively calcul
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
commit c5211187f7ff8e8dbff4ebf7c011ac4c0ffe319c upstream.
If the write endpoint is interrupt type, usb_sndintpipe() should
be passed to usb_fill_int_urb() instead of usb_sndbulkpipe().
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Vrabel
commit a349e23d1cf746f8bdc603dcc61fae9ee4a695f6 upstream.
In 32 bit guests, if a userspace process has %eax == -ERESTARTSYS
(-512) or -ERESTARTNOINTR (-513) when it is interrupted
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Shin
commit 1e779aabe1f0768c2bf8f8c0a5583679b54a upstream.
On systems with very large memory (1 TB in our case), BIOS may report a
reserved region or a hole in the E820 map, even abov
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit f39c1bfb5a03e2d255451bff05be0d7255298fa4 and
commit 84e28a307e376f271505af65a7b7e212dd6f61f4 upstream.
Commit 43cedbf0e8dfb9c5610eb7985d5f21263e313802 (SUNRPC: Ensure tha
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit cd0b16c1c3cda12dbed1f8de8f1a9b0591990724 upstream.
If the filehandle is stale, or open access is denied for some reason,
nlm_fopen() may return one of the NLMv4-specific
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Metcalf
commit 627072b06c362bbe7dc256f618aaa63351f0cfe6 upstream.
The tile tool chain uses the .eh_frame information for backtracing.
The vmlinux build drops any .eh_frame sections at lin
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit fdc858a466b738d35d3492bc7cf77b1dac98bf7c upstream.
The sharpsl_pcmcia_ops structure gets passed into
sa11xx_drv_pcmcia_probe, where it gets accessed at run-time,
unlike all
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
commit 212ba90696ab4884e2025b0b13726d67aadc2cd4 upstream.
The buffer size in read_flush() is too small for the longest possible values
for it. This can lead to a kernel stack corrup
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit c985cb37f1b39c2c8035af741a2a0b79f1fbaca7 upstream.
Because of a change in the s390 arch backend of binutils (commit 23ecd77
"Pick the default arch depending on the target
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 44009105081b51417f311f4c3be0061870b6b8ed upstream.
The "event" variable is a u16 so the shift will always wrap to zero
making the line a no-op.
Signed-off-by: Dan Carpente
On Thu, Oct 25, 2012 at 08:11:12PM -0400, Ric Wheeler wrote:
>
> Sending this just to you two to avoid embarrassing myself if I
> misread the thread, but
>
> Can we reproduce this with any other hardware RAID card? Or with MD?
There was another user who reported very similar corruption using
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Czerner
commit 5de35e8d5c02d271c20e18337e01bc20e6ef472e upstream.
Currently if len argument in ext4_trim_fs() is smaller than one block,
the 'end' variable underflow. Avoid that by return
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
[ Upstream commit 55c2770e413e96871147b9406a9c41fe9bc5209c ]
we want syscall_trace_leave() called on exit from any syscall;
skipping its call in case we'd done force_successful_syscall
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Graham Gower
[ Upstream commit a2af139ff1cd85df586690ff626619ab1ee88b0a ]
Marvell 88E8001 on an ASUS P5NSLI motherboard is unable to send/receive
packets on a system with >4gb ram unless a 32b
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit e793d8c6740f8fe704fa216e95685f4d92c4c4b9 ]
There was a serious disconnect in the logic happening in
sparc_pmu_disable_event() vs. sparc_pmu_enable_event().
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 08280e6c4c2e8049ac61d9e8e3536ec1df629c0d ]
If the MM is not active, only report the top-level PC. Do not try to
access the address space.
Signed-off-by: D
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit c181bc5b5d5c79b71203cd10cef97f802fb6f9c1 upstream.
Adding cmd_ring_state for command ring. It helps to verify
the current command ring state for controlling the command
ring ope
Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 80.110944] Dumping ftrace buffer:
[ 80.110944](ftrace buffer empty)
[ 80.110944] CPU 1
[ 80.110944] Pid: 6452, comm: trinity-child84 Tainted: GW
3.7.0-rc2-next-20121025-sasha-1-g673f98e-dirty #77
[ 80.110944] RIP:
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 2856cc2e4d0852c3ddaae9dcb19cb9396512eb08 ]
On a 2-node machine with 256GB of ram we get 512 lines of
console output, which is just too much.
This mimicks Y
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Kosina
[ Upstream commit a27032eee8cb6e16516f13c8a9752e9d5d4cc430 ]
There are multiple errors in how sys_sparc64_personality() handles
personality flags stored in top three bytes.
- dire
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kuznetsov
[ Upstream commit 4c67525849e0b7f4bd4fab2487ec9e43ea52ef29 ]
After commit e2446eaa ("tcp_v4_send_reset: binding oif to iif in no
sock case").. tcp resets are always lost, when
This patch introduces one module parameter of 'path' in firmware_class
to support customizing firmware image search path, so that people can
use its own firmware path if the default built-in paths can't meet their
demand[1], and the typical usage is passing the below from kernel command
parameter w
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "ramesh.naga...@gmail.com"
[ Upstream commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c ]
The retry loop in neigh_resolve_output() and neigh_connected_output()
call dev_hard_header() with out re
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 44009105081b51417f311f4c3be0061870b6b8ed upstream.
The "event" variable is a u16 so the shift will always wrap to zero
making the line a no-op.
Signed-off-by: Dan Carpente
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit b63f4053cc8aa22a98e3f9a97845afe6c15d0a0d upstream.
According to xHCI spec section 4.6.1.1 and section 4.6.1.2,
after aborting a command on the command ring, xHC will
generate a
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "jeff.liu"
[ Upstream commit 5175a5e76bbdf20a614fb47ce7a38f0f39e70226 ]
This is the revised patch for fixing rds-ping spinlock recursion
according to Venkat's suggestions.
RDS ping/pong over
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit 6e4468b9a0793dfb53eb80d9fe52c739b13b27fd upstream.
The patch is used to cancel command when the command isn't
acknowledged and a timeout occurs.
This patch should be backported
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit b92cc66c047ff7cf587b318fe377061a353c120f upstream.
Software have to abort command ring and cancel command
when a command is failed or hang. Otherwise, the command
ring will hang
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit fdc858a466b738d35d3492bc7cf77b1dac98bf7c upstream.
The sharpsl_pcmcia_ops structure gets passed into
sa11xx_drv_pcmcia_probe, where it gets accessed at run-time,
unlike all
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream.
The min/max call needed to have explicit types on some architectures
(e.g. mn10300). Use clamp_t instead to avoid the warning
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Boullis
commit 301a29da6e891e7eb95c843af0ecdbe86d01f723 upstream.
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
Signed-off
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
commit c5211187f7ff8e8dbff4ebf7c011ac4c0ffe319c upstream.
If the write endpoint is interrupt type, usb_sndintpipe() should
be passed to usb_fill_int_urb() instead of usb_sndbulkpipe().
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Shin
commit 1e779aabe1f0768c2bf8f8c0a5583679b54a upstream.
On systems with very large memory (1 TB in our case), BIOS may report a
reserved region or a hole in the E820 map, even abov
devfreq governors such as ondemand are controlled by a min and
max frequency, while governors like userspace governor allow us
to set a specific frequency.
However, for the same specific device, depending on the SoC, the
available frequencies can vary.
So expose the available frequencies as a snap
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 2702b1526c7278c4d65d78de209a465d4de2885e upstream.
Calling uname() with the UNAME26 personality set allows a leak of kernel
stack contents. This fixes it by defensively calcul
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Morton
commit 168bfeef7bba3f9784f7540b053e4ac72b769ce9 upstream.
If none of the elements in scrubrates[] matches, this loop will cause
__amd64_set_scrub_rate() to incorrectly use the n+1
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts 12d63702c53bc2230dfc997e91ca891f39cb6446 which was commit
303a7ce92064c285a04c870f2dc0192fdb2968cb upstream.
Taking hostname from uts namespace if not safe, beca
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jesse Barnes
commit 3bcf603f6d5d18bd9d076dc280de71f48add4101 upstream.
On CougarPoint and PantherPoint PCH chips, the timing generator may fail
to start after DP training completes. This is du
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Devin Heitmueller
commit a595c1ce4c9d572cf53513570b9f1a263d7867f2 upstream.
We weren't checking whether the resource was in use before calling
res_free(), so applications which called STREAMOFF
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit cd0b16c1c3cda12dbed1f8de8f1a9b0591990724 upstream.
If the filehandle is stale, or open access is denied for some reason,
nlm_fopen() may return one of the NLMv4-specific
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Daisuke Nishimura
commit 1f5320d5972aa50d3e8d2b227b636b370e608359 upstream.
notify_on_release must be triggered when the last process in a cgroup is
move to another. But if the first(and only)
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 4b35f1c52943851b310afb09047bfe991ac8f5ae upstream.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
drivers/usb/serial/option.c | 18 ++
1
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 1452df6f1b7e396d89c2a1fdbdc0e0e839f97671 upstream.
Based on information from the ZTE Windows drivers.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
driv
Hi Christoph,
On Thu, Oct 25, 2012 at 03:19:27PM +, Christoph Lameter wrote:
> On Thu, 25 Oct 2012, Minchan Kim wrote:
>
> > #endif
> > + /*
> > +* True if page in this vma is reclaimed.
>
> What does that mean? All pages in the vma have been cleared out?
It means at least, more than
Hi Linus,
Just radeon fixes in this one,
some new PCI IDs,
ATPX regression fix,
async VM regression fixes
some module options fixes.
Dave.
The following changes since commit b8e902f24fdd16c4373ddc37a4e150c4afe9c6db:
drm/ttm: Fix a theoretical race in ttm_bo_cleanup_refs() (2012-10-23 10:15:2
On Thu, Oct 25, 2012 at 06:41:08PM -0400, Nick Bowler wrote:
> On 2012-10-25 16:29 -0500, Josh Cartwright wrote:
> > On Thu, Oct 25, 2012 at 04:17:01PM -0400, Nick Bowler wrote:
> > > Did you test this on any real hardware? I can't get the ZC702 to work
> > > with the UART mapped at this address (
于 2012年10月26日 02:50, Greg KH 写道:
> On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
>> On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
>>> We are still maintaining the SCSI driver for Realtek card reader,
>>> and will release the latest source code in the Github in the future.
Hi Linus,
This pull fixes a fairly urgent issue with the NFSv2/v3 statd code that
is causing Oopses, as well as some long standing races with the SUNRPC
tcp code.
The following changes since commit 0e9e3e306c7e472bdcffa34c4c4584301eda03b3:
Merge tag 'stable/for-linus-3.7-rc2-tag' of
git://git
On Thu, 2012-10-25 at 14:55 -0400, Vivek Goyal wrote:
> On Thu, Oct 25, 2012 at 02:40:21PM -0400, Mimi Zohar wrote:
> > On Thu, 2012-10-25 at 10:10 -0400, Vivek Goyal wrote:
> > > On Thu, Oct 25, 2012 at 02:10:01AM -0400, Mimi Zohar wrote:
> > >
> > > [..]
> > > > IMA-appraisal verifies the integr
Hi Jiri,
On Sat, 20 Oct 2012 16:33:08 +0200, Jiri Olsa wrote:
> hi,
> adding support to read sample values through the PERF_SAMPLE_READ
> sample type. It's now possible to specify 'S' modifier for an event
> and get its sample value by PERF_SAMPLE_READ.
I have a question. What's an actual impact
Hi, KOSAKI
On 09/28/2012 06:03 AM, KOSAKI Motohiro wrote:
> (9/27/12 2:47 AM), Lai Jiangshan wrote:
>> Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
>> it forgets to manage node_states[N_NORMAL_MEMORY]. it causes
>> node_states[N_NORMAL_MEMORY] becomes stale.
>
> What's m
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
> On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
> > Hi Chen,
> >
> > > But how can bdi related ra_pages reflect different files' readahead
> > > window? Maybe these different files are sequential read, random read
> > >
On Wed, 24 Oct 2012 14:19:37 +0100
Ian Campbell wrote:
> Squeezing the necessary fields into the existing XENMEM_add_to_physmap
> interface was proving to be a bit tricky so we have decided to go with
> a new interface upstream (the XENMAPSPACE_gmfn_foreign interface using
> XENMEM_add_to_physmap
On Thu, 25 Oct 2012 08:46:59 +0100
Ian Campbell wrote:
> On Thu, 2012-10-25 at 01:07 +0100, Mukesh Rathor wrote:
> > On Wed, 24 Oct 2012 16:44:11 -0700
> > Mukesh Rathor wrote:
> >
> > > >
> > > > +/* Indexes into space being mapped. */
> > > > +GUEST_HANDLE(xen_ulong_t) idxs;
> > > >
On 10/25/12 18:41, Jun'ichi Nomura wrote:
> With 749fefe677 ("block: lift the initial queue bypass mode on
> blk_register_queue() instead of blk_init_allocated_queue()"),
> add_disk() eventually calls blk_queue_bypass_end().
> This change invokes the following warning when multipath is used.
...
>
On 10/26/2012 05:27 AM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Ni zhan Chen wrote:
On 10/25/2012 02:59 PM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Ni zhan Chen wrote:
I think it maybe caused by your commit [d189922862e03ce: shmem: fix
negative
rss in memcg memory.stat], one question:
Well,
From: Yuanhan Liu
Firstly, this kind of type check doesn't work. It does something similay
like following:
void * __dummy = NULL;
__buf = __dummy;
__dummy is defined as void *. Thus it will not trigger warnings as
expected.
Second, we don't need that kind of check. Since the pro
On 10/25/2012 12:17 PM, KOSAKI Motohiro wrote:
> On Wed, Oct 24, 2012 at 5:43 AM, Lai Jiangshan wrote:
>> Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
>> it forgets to manage node_states[N_NORMAL_MEMORY]. it may cause
>> node_states[N_NORMAL_MEMORY] becomes incorrect.
>>
>
On 10/26/2012 05:48 AM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Johannes Weiner wrote:
On Wed, Oct 24, 2012 at 09:36:27PM -0700, Hugh Dickins wrote:
On Wed, 24 Oct 2012, Dave Jones wrote:
Machine under significant load (4gb memory used, swap usage fluctuating)
triggered this...
WARNING: at
On 10/26/2012 08:25 AM, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
But how can bdi related ra_pages reflect different files' readahead
window? Maybe these different files are sequential read, random read
and so on.
It's simple: sequential reads
On Thu, Oct 25, 2012 at 05:11:19PM -0700, Jonathan Nieder wrote:
> Hi,
>
> Greg Kroah-Hartman wrote:
>
> > commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream.
> >
> > The min/max call needed to have explicit types on some architectures
> > (e.g. mn10300). Use clamp_t instead to avoid the wa
Yes, it's a new way to do scheduler test. But why use kernel
threads? The info, total time, run time, wait time, preempt number,
all can be collected from tasks' sched info from /proc/pid/sched and
/proc/pid/stat.
I don't understand clearly about "pure scheduler performance" here. In
order to
On 10/25/2012 04:17 PM, Linus Torvalds wrote:
On Thu, Oct 25, 2012 at 5:16 AM, Peter Zijlstra wrote:
From: Rik van Riel
@@ -306,11 +306,26 @@ int ptep_set_access_flags(struct vm_area
pte_t entry, int dirty)
{
int changed = !pte_same(*ptep, entry);
+
On 10/26/2012 09:27 AM, Fengguang Wu wrote:
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
But how can bdi related ra_pages reflect different files' readahead
window? Maybe these different files are sequenti
On Thu, Oct 25, 2012 at 02:08:14AM -0700, Anton Vorontsov wrote:
> Hello Minchan,
>
> Thanks a lot for the email!
>
> On Thu, Oct 25, 2012 at 03:40:09PM +0900, Minchan Kim wrote:
> [...]
> > > What applications (well, activity managers) are really interested in is
> > > this:
> > >
> > > 1. Do w
On Thu, Oct 25, 2012 at 5:46 PM, Ming Lei wrote:
> struct file *file;
> - snprintf(path, PATH_MAX, "%s/%s", fw_path[i], buf->fw_id);
> +
> + if (i < 0) {
> + if (!fw_path_para[0]) /* No customized path */
> +
The benchmark:
/*
* test.c - Simulate workloads that load the CPU differently
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; version 2 of the License.
*
* This pr
On Thu, Oct 25, 2012 at 09:15:58PM -0400, Mimi Zohar wrote:
> On a running system, the package installer, after verifying the package
> integrity, would install each file with the associated 'security.ima'
> extended attribute. The 'security.evm' digital signature would be
> installed with an HMA
On Thu, Oct 25, 2012 at 5:57 PM, Michal Hocko wrote:
> On Wed 24-10-12 11:44:17, Qiang Gao wrote:
>> On Wed, Oct 24, 2012 at 1:43 AM, Balbir Singh wrote:
>> > On Tue, Oct 23, 2012 at 3:45 PM, Michal Hocko wrote:
>> >> On Tue 23-10-12 18:10:33, Qiang Gao wrote:
>> >>> On Tue, Oct 23, 2012 at 5:50
On Fri, Oct 26, 2012 at 09:10:45AM +0800, wwang wrote:
> 于 2012年10月26日 02:50, Greg KH 写道:
> > On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
> >> On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
> >>> We are still maintaining the SCSI driver for Realtek card reader,
> >>> and
于 2012年10月26日 10:45, Greg KH 写道:
On Fri, Oct 26, 2012 at 09:10:45AM +0800, wwang wrote:
于 2012年10月26日 02:50, Greg KH 写道:
On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
We are still maintaining the SCSI driver for Realtek c
From: Yanmin Zhang
We hit a kernel panic at __run_hrtimer=>BUG_ON(timer->state !=
HRTIMER_STATE_CALLBACK).
<2>[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
<0>[ 10.235682, 3] invalid opcode: [#1] PREEMPT SMP
<4>[ 10.240716
On Thu, Oct 25, 2012 at 7:30 PM, Rik van Riel wrote:
>>
>> LOOK at the code, for chrissake. Just look at it. And if you don't see
>> why the above is stupid and retarded, you damn well shouldn't be
>> touching VM code.
>
> I agree it is pretty ugly. However, the above patch
> did get rid of a gig
On 26 October 2012 03:14, Francesco Lavra wrote:
> Hi,
> Hongbo Zhang wrote:
>> Problem of using this list is that the cpufreq_get_max_state callback will be
>> called when register cooling device by thermal_cooling_device_register, but
>> this list isn't ready at this moment. What's more, there i
On 10/26/2012 03:51 AM, Johannes Weiner wrote:
On Thu, Oct 25, 2012 at 05:44:31PM +0100, Will Deacon wrote:
On x86 memory accesses to pages without the ACCESSED flag set result in the
ACCESSED flag being set automatically. With the ARM architecture a page access
fault is raised instead (and it w
On Fri, Oct 26, 2012 at 10:32 AM, Linus Torvalds
wrote:
>
> Please just make "fw_path[0]" just be the pointer to fw_path_para[]
> (which sounds like the cleanest fix) and get rid of the negative 'i'
> and conditional entirely.
Yes, it should be the cleanest, I don't do it because I thought that m
Thank you for comment.
I will make and send patch again.
Thanks and Regards.
SeongJae Park.
On Fri, Oct 26, 2012 at 4:16 AM, Greg KH wrote:
> On Thu, Oct 25, 2012 at 02:51:10PM +0900, SeongJae Park wrote:
>> Nobody use CsrEventHandle, Nobody call function using it as parameter.
>> So, remove it.
Fixes some minor issues in the x86 boot documentation.
Signed-off-by: Kees Cook
---
Documentation/x86/boot.txt |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
index 9efceff..f15cb74 100644
--- a/Documentation/x86/
On 10/26/2012 10:27 AM, Charles Wang wrote:
> Yes, it's a new way to do scheduler test. But why use kernel
> threads? The info, total time, run time, wait time, preempt number, all
> can be collected from tasks' sched info from /proc/pid/sched and
> /proc/pid/stat.
That's right, next version's ST
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/Kconfig between commit a3b8d4a51357 ("GPIO: Add support for GPIO
on CLPS711X-target platform") from the gpio-lw tree and commit
4a8355c4c34f ("ARM: clps711x: convert to clockevents") from the arm-soc
tree.
I fixed it
From: "H. Peter Anvin"
Subject: Re: [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP
Date: Mon, 22 Oct 2012 17:35:47 -0700
> On 10/22/2012 02:29 PM, Eric W. Biederman wrote:
>>>
>>> As I said, I thought Fenghua tried that but it didn't work,
>>> experimentally.
>>
>> Fair enough. You desc
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mach-ux500/cpu-db8500.c between commit 63c53906312f
("pinctrl/nomadik: move the platform data header") from the pinctrl tree
and commit 4040d10a3d44 ("ARM: ux500: add DB serial number to entropy
pool") from the arm-soc
On 10/23/2012 07:53 PM, Josh Cartwright wrote:
> The list of attributes above details the use of the 'filter-ranges'
> property, but the example improperly used 'filter-latency'. Make these
> consistent by fixing up the example.
>
> Signed-off-by: Josh Cartwright
Applied for 3.8 (unless I get m
On Fri, Oct 26, 2012 at 10:30 AM, Ni zhan Chen wrote:
> On 10/26/2012 09:27 AM, Fengguang Wu wrote:
>>
>> On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
>>>
>>> On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
> But how can bdi related ra_pag
On 26 October 2012 05:43, Rafael J. Wysocki wrote:
> I have applied this patch only because of the fixes on top of it. It broke
> kernel compliation due to some missing EXPORT_SYMBOL_GPLs in
> cpufreq_governor.c,
> so I woulnd't have applied it otherwise.
Hi Rafael,
So sorry for this. I am re
701 - 800 of 857 matches
Mail list logo
