3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Junxiao Bi
commit 3e5d3c35a68c9a933bdbdd8685bd1a205b57e806 upstream.
The unaligned io flag is set in the kiocb when an unaligned
dio is issued, it should be cleared even when the dio fails,
or
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit ec01d738a1691dfc85b96b9f796020267a7be577 upstream.
When the server doesn't advertise CAP_LARGE_READ_X, then MS-CIFS states
that you must cap the size of the read at the clien
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
[ Upstream commit cc9b17ad29ecaa20bfe426a8d4dbfb94b13ff1cc ]
We need to validate the number of pages consumed by data_len, otherwise frags
array could be overflowed by userspace. So
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
[ Upstream commit 20e2a86485967c385d7c7befc1646e4d1d39362e ]
When NetLabel is not enabled, e.g. CONFIG_NETLABEL=n, and the system
receives a CIPSO tagged packet it is dropped (cipso_
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: stephen hemminger
[ Upstream commit 149ddd83a92b02c658d6c61f3276eb6500d585e8 ]
This ensures that bridges created with brctl(8) or ioctl(2) directly
also carry IFLA_LINKINFO when dumped over net
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Graf
[ Upstream commit d189634ecab947c10f6f832258b103d0bbfe73cc ]
/proc/net/ipv6_route reflects the contents of fib_table_hash. The proc
handler is installed in ip6_route_net_init() wher
This fixes below build error when CONFIG_MFD_88PM800=m.
ERROR: "pm80x_regmap_config" [drivers/mfd/88pm800.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
Signed-off-by: Axel Lin
---
drivers/mfd/88pm80x.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 9ab4233dd08036fe34a89c7dc6f47a8bf2eb29eb upstream.
Otherwise the code races with munmap (causing a use-after-free
of the vma) or with close (causing a use-after-free of t
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Mason
commit b6305567e7d31b0bec1b8cb9ec0cadd7f7086f5f upstream.
While we are resolving directory modifications in the
tree log, we are triggering delayed metadata updates to
the filesyste
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 48f8b641297df49021093763a3271119a84990a2 upstream.
The intent here was clearly to set result to true if the 0x4000 flag
was set. But instead there was a | vs & typo an
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rustad
commit 863555be0c81558b1af277addcf68acb8f778860 upstream.
Use rcu_dereference_protected to tell rcu that the ft_lport_lock
is held during ft_lport_create. This resolved "suspicious
When tmpfs has the memory policy interleaved it always starts allocating at each
file at node 0. When there are many small files the lower nodes fill up
disproportionately.
This patch spreads out node usage by starting files at nodes other then 0.
The tmpfs superblock grants an offset for each ino
On Thu 05-07-12 02:44:55, Johannes Weiner wrote:
> Once charged, swapcache pages can only be uncharged after they are
> removed from swapcache again.
>
> Do not try to uncharge pages that are known to be in the swapcache, to
> allow future patches to remove checks for that in the uncharge code.
>
The tmpfs superblock grants an offset for each inode as they are created. Each
inode then uses that offset to provide a preferred first node for its interleave
in the newly provided shmem_interleave.
Cc: Christoph Lameter
Cc: Nick Piggin
Cc: Hugh Dickins
Cc: Lee Schermerhorn
Cc: KOSAKI Motohir
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Rosenberg
commit 67de956ff5dc1d4f321e16cfbd63f5be3b691b43 upstream.
Fix multiple remotely-exploitable stack-based buffer overflows due to
the NCI code pulling length fields directly from in
On 7/9/12 8:39 AM, Avi Kivity wrote:
On 07/09/2012 05:24 PM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 17:19 +0300, Gleb Natapov wrote:
Yes, this is knows problem that I can't find time to fix. The crash is
cause by CPU using host PEBS virtual address while guest is running
which causes guest
On Mon, 2012-07-09 at 17:39 +0300, Avi Kivity wrote:
> > Disabling PEBS events for guests isn't pretty though..
>
> We already have atomic MSR switching at guest entry/exit time. So it's
> not pretty in terms of not getting full profiling, but the code won't be
> too hard. Basically we just hav
On Mon, 2012-07-09 at 22:43 +0900, OGAWA Hirofumi wrote:
> "Steven J. Magnani" writes:
>
> >> We need the key, possible key is - if it is only directory, FAT may be
> >> able to use i_start as additional search key.
> >
> > Interesting idea. I think this, and reformulating the FAT NFS file
> > h
On Fri, Jun 22, 2012 at 05:14:45PM +0100, Stefano Stabellini wrote:
> On ARM irqs are not enabled by default:
Which IRQs? Xen IRQs? Linux IRQs?
>
> - call enable_percpu_irq for IRQ_EVTCHN_CALLBACK;
Why do we want to do that?
>
> - set the IRQF_VALID flag for the other irqs bound to evtchns. It
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Vetter
commit 9f846a16d213523fbe6daea17e20df6b8ac5a1e5 upstream.
Especially vesafb likes to map everything as uc- (yikes), and if that
mapping hangs around still while we try to map the
Updating shmem_get_policy to use the vma_policy if provided.
This is to allows us to safely provide shmem_vm_ops to the vma when the vm_file
has not been setup which is the case on the pseudo vmas.
Cc: Christoph Lameter
Cc: Nick Piggin
Cc: Hugh Dickins
Cc: Lee Schermerhorn
Cc: KOSAKI Motohiro
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 332a2e1244bd08b9e3ecd378028513396a004a24 upstream.
We already use them for openat() and friends, but fchdir() also wants to
be able to use O_PATH file descriptors. This s
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 03e934f620101ca2cfc9383bd76172dd3e1f8567 upstream.
Sasha Levin reported following panic :
[ 2136.383310] BUG: unable to handle kernel NULL pointer dereference at
00
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Neuling
commit 2f584a146a2965b82fce89b8d2f95dc5cfe468d0 upstream.
Since we are taking a registers, this should never have been an sldi.
Talking to paulus offline, this is the correct fi
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit f63d7dabd5da9ef41f28f6d69b29bc084db0ca5a upstream.
The latest Realtek driver for the RTL8188CU and RTL8192CU chips adds three
new USB IDs.
Reported-by: Xose Vazquez Perez
On Fri, Jun 22, 2012 at 05:14:42PM +0100, Stefano Stabellini wrote:
> Use Xen features to figure out if we are privileged.
Is there a corresponding Xen c/s for the XNEFEAT_dom0?
Why can't the existing SIF_PRIVILIGED call work? Isn't that
somethign that the hypervisor sets for the guest?
>
> Sig
On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
>
> I found this testing changes to perf-kvm, but found the problem extends
> to just perf-record. With perf-record exclude_guest defaults to 1. See
> tools/perf/util/util.c, event_attr_init().
You lost me there.. so perf-record defaults to
On Fri, Jun 22, 2012 at 05:14:40PM +0100, Stefano Stabellini wrote:
> Fix the shared_info and vcpu_info struct definitions to match the ones
> in Xen.
Is there a corresponding c/s in the Xen tree for this?
>
> Signed-off-by: Stefano Stabellini
> ---
> arch/arm/include/asm/xen/interface.h | 1
On 07/09/2012 05:49 PM, Peter Zijlstra wrote:
> On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
>>
>> I found this testing changes to perf-kvm, but found the problem extends
>> to just perf-record. With perf-record exclude_guest defaults to 1. See
>> tools/perf/util/util.c, event_attr_init
On 07/09/2012 08:40 AM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 14:23 +0200, Peter Zijlstra wrote:
It is not yet clear to me how and why your code converges.
I don't think it does.. but since the scheduler interaction is fairly
weak it doesn't matter too much from that pov.
Fair enough.
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit 1850753d2e6d9ca7856581ca5d3cf09521e6a5d7 upstream.
In ops_run_io(), the call to md_wait_for_blocked_rdev will decrement
nr_pending so we lose the reference we hold on the rdev
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit bc1d7702910c7c7e88eb60b58429dbfe293683ce upstream.
We have a bug report where the kernel hits a warning in the cpumask
code:
WARNING: at include/linux/cpumask.h:107
Whi
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 4b5ebccc40843104d980f0714bc86bfcd5568941 upstream.
When receiving an "individually addressed" action frame, the
receiver is required to return it to the sender. mac80211
ge
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 055d3747dbf00ce85c6872ecca4d466638e80c22 upstream.
commit 58c54fcca3bac5bf9290cfed31c76e4c4bfbabaf
md/raid10: handle further errors during fix_read_error better.
in 3.1 a
This is the start of the stable review cycle for the 3.2.23 release.
There are 48 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Jul 11 20:00:00 UTC 2012.
Anything receiv
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Panayiotis Karabassis
commit 7508b657967cf664b5aa0f6367d05016e7e3bc2a upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=42903
Based on the work of
Signed-off-by: Panayiotis Karabassis
S
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Hebbar, Gururaja"
commit c9fe573a6584034670c1a55ee8162d623519cbbf upstream.
In sound/soc/codecs/tlv320aic3x.c
data = snd_soc_read(codec, AIC3X_PLL_PROGA_REG);
snd_soc_write(co
On 7/9/12 8:49 AM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
I found this testing changes to perf-kvm, but found the problem extends
to just perf-record. With perf-record exclude_guest defaults to 1. See
tools/perf/util/util.c, event_attr_init().
You lost me
On Fri, Jun 22, 2012 at 05:14:41PM +0100, Stefano Stabellini wrote:
> We used to rely on a core_initcall to initialize Xen on ARM, however
> core_initcalls are actually called after early consoles are initialized.
> That means that hvc_xen.c is going to be initialized before Xen.
>
> Given the lac
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit fc448a18ae6219af9a73257b1fbcd009efab4a81 upstream.
If a RAID10 has an odd number of chunks - as might happen when there
are an odd number of devices - the last chunk has no pai
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Stone Piao
commit f03ba7e9a24e5e9efaad56bd1713b994ea556b16 upstream.
After association, STA will go through eapol handshake with WPS
enabled AP. It's observed that WPS handshake fails with some
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: majianpeng
commit 6c0544e255dd6582a9899572e120fb55d9f672a4 upstream.
In chunk_aligned_read() we are adding data_offset before calling
is_badblock. But is_badblock also adds data_offset, so tha
On 07/09/2012 08:26 AM, Peter Zijlstra wrote:
On Sun, 2012-07-08 at 14:34 -0400, Rik van Riel wrote:
Do we really want to calculate the amount of CPU time used
by a process, and start migrating after just one second?
Or would it be ok to start migrating once a process has
been scanned once or
3.2-stable review patch. If anyone has any objections, please let me know.
--
From: Stone Piao
commit 925839243dc9aa4ef25305f5afd10ed18258a4ac upstream.
Currently we check the sequence number of last packet received
against start_win. If a sequence hole is detected, start_win
On Mon, Jul 09, 2012 at 05:51:29PM +0300, Avi Kivity wrote:
> On 07/09/2012 05:49 PM, Peter Zijlstra wrote:
> > On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
> >>
> >> I found this testing changes to perf-kvm, but found the problem extends
> >> to just perf-record. With perf-record exclud
On 07/09/2012 08:25 AM, Peter Zijlstra wrote:
On Sun, 2012-07-08 at 14:35 -0400, Rik van Riel wrote:
This looks like something that should be fixed before the
code is submitted for merging upstream.
static bool __task_can_migrate(struct task_struct *t, u64 *runtime, int node)
{
...
is what
On Mon, 2012-07-09 at 10:53 -0400, Rik van Riel wrote:
> On 07/09/2012 08:26 AM, Peter Zijlstra wrote:
> > On Sun, 2012-07-08 at 14:34 -0400, Rik van Riel wrote:
>
> >> Do we really want to calculate the amount of CPU time used
> >> by a process, and start migrating after just one second?
> >>
> >
On Mon, Jul 09, 2012 at 05:54:42PM +0300, Gleb Natapov wrote:
> On Mon, Jul 09, 2012 at 05:51:29PM +0300, Avi Kivity wrote:
> > On 07/09/2012 05:49 PM, Peter Zijlstra wrote:
> > > On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
> > >>
> > >> I found this testing changes to perf-kvm, but foun
blk_set_stacking_limits() is intended to allow stacking drivers to build
up the limits of the stacked device based on the underlying devices'
limits. But in the case of 'max_sectors' the default of
BLK_DEF_MAX_SECTORS (1024) doesn't allow the stacking driver to inherit
a max_sectors larger than 10
On Mon, Jul 09, 2012 at 03:46:59AM +, Li Yang-R58472 wrote:
> > > I don't understand, why is this just showing up now? What changed to
> > > cause this? Couldn't that be the real problem here?
> > >
> >
> > The issue is showing up because we now probe devices twice.
> > Previously, we just p
On 7/9/12 8:52 AM, David Ahern wrote:
On 7/9/12 8:49 AM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
I found this testing changes to perf-kvm, but found the problem extends
to just perf-record. With perf-record exclude_guest defaults to 1. See
tools/perf/util/ut
unsubscribe linux-kernel
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 2012-07-09 at 17:51 +0300, Avi Kivity wrote:
> On 07/09/2012 05:49 PM, Peter Zijlstra wrote:
> > On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
> >>
> >> I found this testing changes to perf-kvm, but found the problem extends
> >> to just perf-record. With perf-record exclude_guest
On Thu 05-07-12 02:44:56, Johannes Weiner wrote:
> Not all uncharge paths need to check if the page is swapcache, some of
> them can know for sure.
>
> Push down the check into all callsites of uncharge_common() so that
> the patch that removes some of them is more obvious.
>
> Signed-off-by: Joh
Recent change in the core driver to get the maximum voltage
is based on the (n_voltages -1) steps of voltage.
For the tps65910, the (n_voltages -1)th step voltage is
calculated based on the callback function list_voltage.
This function direct maps the datasheet and adjust the
first few steps for in
On Thu 05-07-12 02:44:57, Johannes Weiner wrote:
> Only anon pages that are uncharged at the time of the last page table
> mapping vanishing may be in swapcache.
>
> When shmem pages, file pages, swap-freed anon pages, or just migrated
> pages are uncharged, they are known for sure to be not in sw
On 09/07/12 15:45, Konrad Rzeszutek Wilk wrote:
> On Fri, Jun 22, 2012 at 05:14:41PM +0100, Stefano Stabellini wrote:
>> We used to rely on a core_initcall to initialize Xen on ARM, however
>> core_initcalls are actually called after early consoles are initialized.
>> That means that hvc_xen.c is g
On Thu 05-07-12 02:44:58, Johannes Weiner wrote:
> Charging cache pages may require swapin in the shmem case. Save the
> forward declaration and just move the swapin functions above the cache
> charging functions.
>
> Signed-off-by: Johannes Weiner
OK
Acked-by: Michal Hocko
> ---
> mm/memcon
On 9 July 2012 16:37, Shilimkar, Santosh wrote:
> On Mon, Jul 9, 2012 at 8:06 PM, Vincent Guittot
> wrote:
>> On 9 July 2012 15:00, Shilimkar, Santosh wrote:
>>> On Mon, Jul 9, 2012 at 6:02 PM, Vincent Guittot
>>> wrote:
On 9 July 2012 12:55, Shilimkar, Santosh wrote:
> Vincent,
>
On Fri, Jul 06, 2012 at 09:51:16PM -0400, Phillip Susi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> What's the status of this patch? Forgotten, or are there still any
> outstanding concerns?
There was one outstanding concern from maxim about missing "bdput(bdevp)".
Will see if I
On Thu 05-07-12 02:44:59, Johannes Weiner wrote:
> shmem page charges have not needed a separate charge type to tell them
> from regular file pages since 08e552c 'memcg: synchronized LRU'.
>
> Signed-off-by: Johannes Weiner
Yes, MEM_CGROUP_CHARGE_TYPE_SHMEM has been quite confusing.
Acked-by: M
On 7/9/12 8:58 AM, David Ahern wrote:
On 7/9/12 8:52 AM, David Ahern wrote:
On 7/9/12 8:49 AM, Peter Zijlstra wrote:
On Mon, 2012-07-09 at 08:47 -0600, David Ahern wrote:
I found this testing changes to perf-kvm, but found the problem extends
to just perf-record. With perf-record exclude_gues
On Mon, 9 Jul 2012, Yasuaki Ishimatsu wrote:
> Even if you apply these patches, you cannot remove the physical memory
> completely since these patches are still under development. I want you to
> cooperate to improve the physical memory hot-remove. So please review these
> patches and give your c
On Thu 05-07-12 02:45:00, Johannes Weiner wrote:
> It does not matter to __mem_cgroup_try_charge() if the passed mm is
> NULL or init_mm, it will charge the root memcg in either case.
>
> Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
> ---
> mm/memcontrol.c |5 -
> 1 files cha
On Fri, 6 Jul 2012, Greg KH wrote:
> Here's the 006 release of usbutils.
>
> Some USB 3.0 updates, a new usb.ids file update, and a number of other
> fixes and updates for annoying problems that people had reported. Full
> shortlog information is below if people are curious.
>
> The package can
On Thu 05-07-12 02:45:01, Johannes Weiner wrote:
> When shmem is charged upon swapin, it does not need to check twice
> whether the memory controller is enabled.
>
> Also, shmem pages do not have to be checked for everything that
> regular anon pages have to be checked for, so let shmem use the
>
On Mon, Jul 9, 2012 at 8:40 PM, Vincent Guittot
wrote:
> On 9 July 2012 16:37, Shilimkar, Santosh wrote:
>> On Mon, Jul 9, 2012 at 8:06 PM, Vincent Guittot
>> wrote:
>>> On 9 July 2012 15:00, Shilimkar, Santosh wrote:
On Mon, Jul 9, 2012 at 6:02 PM, Vincent Guittot
wrote:
> On 9
On Monday 09 July 2012, Alan Cox wrote:
> > > These are the same reasons the x86_64 people gave and regretted later.
> >
> > I would not compare the x86_64 extension to the AArch64 architecture.
>
>
> It's not an architecture specific observation. I was just observing that
> you were following a
On Thu 05-07-12 02:45:02, Johannes Weiner wrote:
> Only anon and shmem pages in the swap cache are attempted to be
> charged multiple times, from every swap pte fault or from
> shmem_unuse(). No other pages require checking PageCgroupUsed().
>
> Charging pages in the swap cache is also serialized
On Thu 05-07-12 02:45:03, Johannes Weiner wrote:
> shmem knows for sure that the page is in swap cache when attempting to
> charge a page, because the cache charge entry function has a check for
> it. Only anon pages may be removed from swap cache already when
> trying to charge their swapin.
>
>
On Thu 05-07-12 02:44:52, Johannes Weiner wrote:
> Hello,
>
> the biggest thing is probably #1, no longer trying (and failing) to
> charge replacement pages during migration and thus compaction. The
> rest is cleanups and tiny optimizations that move some checks out of
> the charge and uncharge c
On 03/07/12 16:40, Konrad Rzeszutek Wilk wrote:
> Running perf tells me that the check for p2m_identity
> is done a lot - more than it should.
This patch doesn't change the how often the check is done. Is this just
bad wording of the description?
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
>
On 06/28/2012 08:55 AM, Andrea Arcangeli wrote:
o reduced the page_autonuma memory overhead to from 32 to 12 bytes per page
This bit still worries me a little.
Between the compact list management code, the migrate
daemon, the list locking and page queuing and unqueuing
code, we are looking at
> I think the main strategy should be to spot duplicate code early
> and make sure we deal with it individually. Examples for this are
> probably the implementations for kvm and perf, which largely deal
> with the same hardware on both architectures. Those definitely must
> not get duplicated into
On Mon, Jul 09, 2012 at 03:02:22PM +0100, Matthew Garrett wrote:
> On Mon, Jul 09, 2012 at 02:56:26PM +0100, Mark Brown wrote:
> > Where is this discussion?
> My part of it has pretty much been in-person discussion with Grant
> Likely, but there was some on ksummit-discuss last month.
Oh, I saw
On Mon, Jul 9, 2012 at 9:08 PM, Jiri Kosina wrote:
>> --- a/drivers/hid/usbhid/hid-quirks.c
>> +++ b/drivers/hid/usbhid/hid-quirks.c
>> + { USB_VENDOR_ID_MADCATZ, USB_DEVICE_ID_MADCATZ_BEATPAD,
>> HID_QUIRK_IGNORE },
>
> Please put it in drivers/hid/hid-core.c, hid_ignore_list[] array instea
On 07/09/2012 03:18 PM, Hillf Danton wrote:
>> Most distros already have or are on the way to switch to systemd.
>
> We have to adapt to distros once more:(
Well they are the customer...
(OK, maybe not _the_ customer, but definitely a major customer).
--
To unsubscribe from this list: send the l
Arnd,
On Mon, Jul 09, 2012 at 04:32:11PM +0100, Arnd Bergmann wrote:
> We have a lot of reviewers that are familiar with the 32 bit code, so
> I think the main strategy should be to spot duplicate code early
> and make sure we deal with it individually. Examples for this are
> probably the impleme
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>> Hello,
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49 box3 ntpd[5067]: parse: convert_rawdcf: INCOMPLETE DAT
"Steven J. Magnani" writes:
> On Mon, 2012-07-09 at 22:43 +0900, OGAWA Hirofumi wrote:
>> "Steven J. Magnani" writes:
>>
>> >> We need the key, possible key is - if it is only directory, FAT may be
>> >> able to use i_start as additional search key.
>> >
>> > Interesting idea. I think this, an
On Mon, Jul 09, 2012 at 03:53:14PM +0200, Toralf Förster wrote:
> After reading [1] I'm wondering whether these would at least improve
> OpenSSL's implementation of a RSA key generator (page 13 in [1]) ?
Random PID's is a terribly way to get entropy into OpenSSL. You don't
get that many bits of e
On Mon, Jul 09, 2012 at 04:41:24PM +0100, David Vrabel wrote:
> On 03/07/12 16:40, Konrad Rzeszutek Wilk wrote:
> > Running perf tells me that the check for p2m_identity
> > is done a lot - more than it should.
>
> This patch doesn't change the how often the check is done. Is this just
> bad word
> This makes mi->restartable unused?
It does ... but it's not what I meant ... somehow I lost the code that set
MF_MUST_KILL
based on mi->restartable. Doh!
>> +doit = !!PageDirty(ppage) || (flags & MF_MUST_KILL) != 0;
>
> Maybe
>
>!!(flags & MF_MUST_KILL)
On Tue, 2012-07-10 at 01:10 +0900, OGAWA Hirofumi wrote:
> "Steven J. Magnani" writes:
>
> > On Mon, 2012-07-09 at 22:43 +0900, OGAWA Hirofumi wrote:
> >> "Steven J. Magnani" writes:
> >>
> >> >> We need the key, possible key is - if it is only directory, FAT may be
> >> >> able to use i_star
On Monday 09 July 2012, Catalin Marinas wrote:
> On Mon, Jul 09, 2012 at 04:32:11PM +0100, Arnd Bergmann wrote:
> > We have a lot of reviewers that are familiar with the 32 bit code, so
> > I think the main strategy should be to spot duplicate code early
> > and make sure we deal with it individual
On Sun, Jul 08, 2012 at 11:58:46AM +0300, Shachar Shemesh wrote:
> On 07/07/2012 12:24 AM, Greg KH wrote:
> >On Sun, Jul 01, 2012 at 09:53:19AM +0300, Shachar Shemesh wrote:
> >>From: Shachar Shemesh
> >>
> >>Commit acfa747b introduced the TTY_HUPPING flag to distinguish
> >>closed TTY from curren
On 07/08/2012 08:23 PM, Jason Wang wrote:
On 07/07/2012 12:23 AM, Rick Jones wrote:
On 07/06/2012 12:42 AM, Jason Wang wrote:
Which mechanism to address skew error? The netperf manual describes
more than one:
This mechanism is missed in my test, I would add them to my test scripts.
http://w
The kernel no longer allows us to pass NULL for the hard handler
without also specifying IRQF_ONESHOT. IRQF_ONESHOT imposes latency
in the exit path that we don't need for MSI interrupts. Long term
we'd like to inject these interrupts from the hard handler when
possible. In the short term, we ca
On Mon, Jul 09, 2012 at 11:04:42AM +0100, Mel Gorman wrote:
> > - lets assume your allocation happens with kmalloc() without __GFP_MEMALLOC
> > and current->flags has PF_MEMALLOC ORed and your SLAB pool is empty. This
> > forces SLAB to allocate more pages from the buddy allocator with it will
On Mon, Jul 9, 2012 at 4:05 AM, Jiang Liu wrote:
> Hi Bjorn and Yinghai,
> What's the policy to export a symbol by EXPORT_SYMBOL()
> or EXPORT_SYMBOL_GPL()? I know the legal difference, but don't
> know when I should mark a symbol as GPL.
>From Documentation/DocBook/kernel-hacking.tmpl,
On Mon, 2012-07-09 at 11:27 -0500, Steven J. Magnani wrote:
> On Tue, 2012-07-10 at 01:10 +0900, OGAWA Hirofumi wrote:
> > "Steven J. Magnani" writes:
> >
> > > On Mon, 2012-07-09 at 22:43 +0900, OGAWA Hirofumi wrote:
> > >> "Steven J. Magnani" writes:
> > >>
> > >> >> We need the key, possi
On Sun, Jul 08, 2012 at 07:55:55PM +0200, Kay Sievers wrote:
> On Sat, 2012-07-07 at 07:04 +1000, Michael Neuling wrote:
> > Whole kmsg below.
>
> I guess I have an idea now what's going on.
>
> > 4,47,0;WARNING: at
> > /scratch/mikey/src/linux-ozlabs/arch/powerpc/sysdev/xics/xics-common.c:105
>
On Wed, Jul 04, 2012 at 01:40:39PM +0800, Li Zefan wrote:
> Tejun Heo wrote:
>
> >>From 6da2689412c78b97716ec524cc30baf7b46508cd Mon Sep 17 00:00:00 2001
> > From: Tejun Heo
> > Date: Tue, 3 Jul 2012 10:32:26 -0700
> >
> > While refactoring cgroup file removal path, 05ef1d7c4a "cgroup:
> > intro
On Mon, 2012-07-09 at 10:09 -0700, Greg Kroah-Hartman wrote:
> is it ok if we
> just merge this in 3.6-rc1 and backport it to 3.5.1 if it looks ok
> there?
I'd prefer it get accepted now so that refactoring the
printk subsystem could occur for 3.6.
Another option would be to revert all Kay's chan
On Mon, Jul 02, 2012 at 10:29:27AM -0400, Aristeu Rozanski wrote:
> From: Li Zefan
>
> When remounting cgroupfs with some subsystems added to it and some
> removed, cgroup will remove all the files in root directory and then
> re-popluate it.
>
> What I'm doing here is, only remove files which b
On Mon, Jul 09, 2012 at 10:17:48AM -0700, Tejun Heo wrote:
> On Mon, Jul 02, 2012 at 10:29:27AM -0400, Aristeu Rozanski wrote:
> > From: Li Zefan
> >
> > When remounting cgroupfs with some subsystems added to it and some
> > removed, cgroup will remove all the files in root directory and then
> >
On Mon, 2012-07-09 at 12:09 -0500, Steven J. Magnani wrote:
> On Mon, 2012-07-09 at 11:27 -0500, Steven J. Magnani wrote:
> > On Tue, 2012-07-10 at 01:10 +0900, OGAWA Hirofumi wrote:
> > > If the inode is not on cache anymore, is there the possibility that
> > > selects the wrong parent? IIRC, N
Hello,
Ever since 3.4.4 I see lots more of:
Jul 9 19:08:01 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:10:07 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:16:44 box4 kernel: r8169 :03:00.0: eth0: link up
Jul 9 19:17:07 box4 kernel: r8169 :03:00.0: eth0: link up
Ju
> looks like they do not bios update for S10 yet.
>
> http://www.panasonic.com/business/toughbook/computer-support-bios.asp#CF-U1
>
> maybe you can try to email or call their support.
Please stop suggesting a BIOS upgrade. The BIOS is totally out of our
control, and if the current BIOS works with
On Mon, Jul 09, 2012 at 10:22:20AM -0700, Tejun Heo wrote:
> > Changing subsys_bits via remount is being deprecated. No need to
> > worry about this.
>
> Also, why does this matter? The xattrs are kept in cgrp anyway. Why
> does keeping dentry/inode around make difference?
Ah, okay, the file x
101 - 200 of 724 matches
Mail list logo
