Hi Mitsuhiro,
On 04/12/2013 09:43 PM, Mitsuhiro Tanino wrote:
(2013/04/11 22:00), Ric Mason wrote:
Hi Mitsuhiro,
On 04/11/2013 08:51 PM, Mitsuhiro Tanino wrote:
(2013/04/11 12:53), Simon Jeons wrote:
One question against mce instead of the patchset. ;-)
When check memory is bad? Before
Hi Alexandre,
Today's linux-next merge of the gen-gpio tree got a conflict in
drivers/usb/otg/Kconfig between commit a0e631235a04 ("usb: phy: move all
PHY drivers to drivers/usb/phy/") from the usb tree and commit
76ec9d18b897 ("Convert selectors of GENERIC_GPIO to GPIOLIB") from the
gen-gpio
Reduce the size of the objects by consolidating
the duplicated USB_STORAGE into a single function.
Add function usb_stor_dbg to emit debugging messages.
Always validate the format and arguments.
Reduce the number of uses of CONFIG_USB_STORAGE_DEBUG.
Reduces size of objects ~7KB when
1) Fix erroneous netfilter drop of SIP packets generated by some Cisco
phones, from Patrick McHardy.
2) Fix netfilter IPSET refcounting in list_set_add(), from Jozsef
Kadlecsik.
3) Fix TCP syncookies route lookup key, we don't use the same values
we would use for the usual SYN receive
Hi Axel
Thanks for the patch
On Wed, 17 Apr 2013, Axel Lin wrote:
> The same table can be used for multiple instance of pdev, so we don't need to
> allocate memory for of_regulator_match table per pdev.
>
> Signed-off-by: Axel Lin
> ---
> drivers/regulator/as3711-regulator.c | 46
>
On Wed, Apr 17, 2013 at 01:25:13PM +0930, Rusty Russell wrote:
Veaceslav Falico writes:
Tested for a day on two reproducers on the latest upstream kernel, with the
recent kobject fix a49b7e82 ("kobject: fix kset_find_obj() race with
concurrent last kobject_put()") - it fixes the issue, no
On 04/11/2013 09:49 PM, Andi Kleen wrote:
As a result, if the dirty cache includes user data, the data is lost,
and data corruption occurs if an application uses old data.
Hi Andi,
Could you give me the link of your mce testcase?
The application cannot use old data, the kernel code kills it
On Tuesday 16 April 2013 11:50 AM, Aruna Balakrishnaiah wrote:
Currently with this patchset, pstore is not supporting compression of
oops-messages
since it involves some changes in the pstore framework.
big_oops_buf will hold the large part of oops data which will be compressed
and put
to
On Tue, 16 Apr 2013 15:25:45 +0200, Oleg Nesterov wrote:
> On 04/16, Frederic Weisbecker wrote:
> > On Sun, Apr 14, 2013 at 09:12:05PM +0200, Oleg Nesterov wrote:
> > Looking at the bug report, it seems they only reproduced with a homemade
> > test. No real app has reported that issue?
>
> iirc
> -Original Message-
> From: Timur Tabi [mailto:ti...@tabi.org]
> Sent: 2013年4月17日 11:31
> To: Tang Yuantian-B29983
> Cc: Grant Likely; devicetree-discuss; linuxppc-...@lists.ozlabs.org; lkml;
> Rob Herring
> Subject: Re: [PATCH v2] of/base: release the node correctly in
>
On Wed, 17 Apr 2013, Yasuaki Ishimatsu wrote:
> > Why not simply do what generic sparsemem support does by testing
> > PageSlab(virt_to_head_page(res)) and calling kfree() if true and freeing
> > back to bootmem if false? This should be like a five line patch.
>
> Is your explanation about
On 04/16/2013 06:33 PM, Luis Henriques wrote:
68d929862e29a8b52a7f2f2f86a0600423b093cd efi: be more paranoid about available
space when creating variables
This prevents a bricking issue for some Samsung devices but causes
regression on many other machines.
In the __mutex_lock_common() function, an initial entry into
the lock slow path will cause two atomic_xchg instructions to be
issued. Together with the atomic decrement in the fast path, a total
of three atomic read-modify-write instructions will be issued in
rapid succession. This can cause a lot
If it is confirmed that all the supported architectures can allow a
negative mutex count without incorrect behavior, we can then back
out the architecture specific change and allow the mutex count to
go to any negative number. That should further reduce contention for
non-x86 architecture.
If
v2->v3
- Add patch 4 to remove new typedefs introduced in patch 2.
- Add patch 5 to remove SCHED_FEAT_OWNER_SPIN and move the mutex
spinning code to mutex.c.
v1->v2
- Remove the 2 mutex spinner patches and replaced it by another one
to improve the mutex spinning process.
- Remove
In response to the review comment from Davidlohr, this patch will
remove the new typedefs introduced by patch 2. It also removes an
unnecessary barrier() call.
Signed-off-by: Waiman Long
---
kernel/mutex.c | 25 +++--
1 files changed, 11 insertions(+), 14 deletions(-)
The current mutex spinning code (with MUTEX_SPIN_ON_OWNER option turned
on) allow multiple tasks to spin on a single mutex concurrently. A
potential problem with the current approach is that when the mutex
becomes available, all the spinning tasks will try to acquire the
mutex more or less
As mentioned by Ingo, the SCHED_FEAT_OWNER_SPIN scheduler feature
bit was really just an early hack to make with/without mutex-spinning
testable. So it is no longer necessary.
This patch removes the SCHED_FEAT_OWNER_SPIN feature bit and move the
mutex spinning code from kernel/sched/core.c back
This patch removes dm_pg_init_complete()'s declaration as it is
not needed anymore since 2651f5d7d3bc5120a439e498f131e4d731f99b3e.
Signed-off-by: Ren Mingxin
---
drivers/md/dm-mpath.h |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/drivers/md/dm-mpath.h
also please help checking this patch, when you have time.
thanks.
On 2013年04月12日 16:56, Chen Gang wrote:
>
> need call audit_put_tree, if tree is valid.
> just like another area have done in function audit_add_rule.
>
> Signed-off-by: Chen Gang
> ---
> kernel/auditfilter.c |6
in function audit_data_to_entry:
when failure occurs, need check and free tree and watch.
or memory leak.
test:
plan:
test command:
"auditctl -a exit,always -w /etc -F auid=-1"
(on fedora17, need modify auditctl to let "-w /etc" has effect)
running:
Hi David,
2013/04/17 9:36, David Rientjes wrote:
On Wed, 17 Apr 2013, Yasuaki Ishimatsu wrote:
When hot removing memory presented at boot time, following messages are shown:
[ 296.867031] [ cut here ]
[ 296.922273] kernel BUG at mm/slub.c:3409!
[ 296.970229]
On 04/16/2013 09:32 PM, James Hogan wrote:
>
> Also, I think you probably now want *.dtb.S added to clean-files,
> otherwise they won't get removed by make clean.
Good catch !
Thx,
-Vineet
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi James,
On 04/16/2013 09:23 PM, James Hogan wrote:
> On 12/04/13 22:52, Stephen Warren wrote:
>> +.SECONDARY: $(obj)/$(builtindtb-y).dtb.S
> Note, this may not work if you're using CONFIG_ARC_BUILTIN_DTB_NAME,
> since it'll have quotes around it, so you may instead need:
> .SECONDARY:
Veaceslav Falico writes:
> Tested for a day on two reproducers on the latest upstream kernel, with the
> recent kobject fix a49b7e82 ("kobject: fix kset_find_obj() race with
> concurrent last kobject_put()") - it fixes the issue, no regressions met.
Thanks, I've included the fix in my
since "normally audit_add_tree_rule() will free it on failure",
need free it completely, when failure occures.
need additional put_tree before return, since get_tree was called.
always need goto error processing area for list_del_init.
Signed-off-by: Chen Gang
---
On 04/16/2013 10:53 PM, Segher Boessenkool wrote:
>> +/* r3 = n (where n = [0-1023])
>> + * The maximum number of BHRB entries supported with PPC_MFBHRBE
>> instruction
>> + * is 1024. We have limited number of table entries here as POWER8
>> implements
>> + * 32 BHRB entries.
>> + */
>> +
>> +/*
From: Namhyung Kim
The header_page file describes the format of the ring buffer page
which is used by ftrace (not perf). And size of "commit" field (I
guess it's older name was 'size') represents the real size of long
type used for kernel. So update the pevent's long size.
Signed-off-by:
On Tue, 16 Apr 2013 20:41:59 -, Michael Witten wrote:
> On Tue, 16 Apr 2013 13:32:08 -0700, David Ahern wrote:
>
>> On 4/16/13 10:08 AM, Michael Witten wrote:
>>> You should probably disable python support more directly:
>>>
>>>make NO_LIBPYTHON=1
>>
>> sure, but I should not have to do
Tang Yuantian-B29983 wrote:
>On Tue, Apr 9, 2013 at 10:36 PM, wrote:
> >
> >+ /* Found it! return success */
>
>I'm pretty sure this comment is in the wrong place.
It is not perfect, but acceptable.
Like I said, I'm pretty sure it's in the wrong place.
--
Timur
hi Laxman,
Currently we have below code in tps80031_ldo_set_voltage_sel():
/* Check for valid setting for TPS80031 or TPS80032-ES1.0 */
if ((ri->rinfo->desc.id == TPS80031_REGULATOR_LDO2) &&
(ri->device_flags & TRACK_MODE_ENABLE)) {
Guys, I just pushed out a new helper function intended for cleaning up
various device driver mmap functions, because they are rather messy,
and at least part of the problem was the bad impedance between what a
driver author would want to have, and the VM interfaces to map a
memory range into user
On Fri, Apr 12, 2013 at 03:16:32PM -0400, Jeff Layton wrote:
> Jiri reported a regression in auditing of open(..., O_CREAT) syscalls.
> In older kernels, creating a file with open(..., O_CREAT) created
> audit_name records that looked like this:
>
> type=PATH msg=audit(1360255720.628:64): item=1
On 04/17/2013 02:08 AM, Robin Holt wrote:
> On Tue, Apr 16, 2013 at 09:07:20PM +0800, Xiao Guangrong wrote:
>> On 04/16/2013 07:43 PM, Robin Holt wrote:
>>> Argh. Taking a step back helped clear my head.
>>>
>>> For the -stable releases, I agree we should just go with your
>>>
> -Original Message-
> From: Timur Tabi [mailto:ti...@tabi.org]
> Sent: 2013年4月16日 19:37
> To: Tang Yuantian-B29983
> Cc: Grant Likely; devicetree-discuss; linuxppc-...@lists.ozlabs.org; lkml;
> Rob Herring
> Subject: Re: [PATCH v2] of/base: release the node correctly in
>
On 2013年04月16日 18:38, Chen Gang wrote:
> On 2013年04月16日 18:25, Chen Gang wrote:
>> On 2013年04月12日 17:42, Chen Gang wrote:
>>> On 2013年04月11日 12:10, Chen Gang wrote:
On 2013年04月11日 05:19, Eric Paris wrote:
> - Original Message -
>
>>> b. has an new issue for AUDIT_DIR:
The same table can be used for multiple instance of pdev, so we don't need to
allocate memory for of_regulator_match table per pdev.
Signed-off-by: Axel Lin
---
drivers/regulator/as3711-regulator.c | 46 ++
1 file changed, 19 insertions(+), 27 deletions(-)
OK, thanks.
Thanks,
Yuantian
> -Original Message-
> From: Mike Turquette [mailto:mturque...@linaro.org]
> Sent: 2013年4月17日 6:27
> To: Tang Yuantian-B29983; Tang Yuantian-B29983
> Cc: linus.wall...@linaro.org; viresh.ku...@linaro.org;
> shawn@linaro.org; ulf.hans...@linaro.org;
On Sat, Apr 13, 2013 at 01:20:07PM +0200, Lars-Peter Clausen wrote:
> The pm2301-charger driver implements runtime pm and at the same time uses the
> legacy pm callbacks for suspend and resume. This does not work since the I2C
> core wont look at the legacy pm callbacks if a driver has the 'pm'
On Wed, Mar 27, 2013 at 11:48:21PM +0200, Andrei Epure wrote:
> Patch found using coccinelle.
>
> Signed-off-by: Andrei Epure
> ---
Applied, thanks!
> drivers/power/charger-manager.c |3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/power/charger-manager.c
On Mon, Apr 01, 2013 at 05:45:55PM -0400, Rhyland Klein wrote:
> Adding support for supplied_from char * array. This is meant to store the
> list of suppliers for a given supply, i.e. chargers for a battery. This
> list can be populated through devicetree readily as well as passed
> directly from
On Tue, Apr 02, 2013 at 03:31:30PM -0600, Stephen Warren wrote:
> On 04/01/2013 03:45 PM, Rhyland Klein wrote:
> > This patch adds support for supplies to register a list of char *'s
> > which represent the list of supplies which supply them. This is the
> > opposite as the supplied_to list.
>
>
A memcg may livelock when oom if the process that grabs the hierarchy's
oom lock is never the first process with PF_EXITING set in the memcg's
task iteration.
The oom killer, both global and memcg, will defer if it finds an eligible
process that is in the process of exiting and it is not being
On 2013/4/17 2:27, David Howells wrote:
> Supply an accessor to get the process ID associated with some proc files and
> directories (get_proc_pid()).
>
> Signed-off-by: David Howells
> cc: Tejun Heo
> cc: Li Zefan
> cc: contain...@lists.linux-foundation.org
> cc: cgro...@vger.kernel.org
On Thu, Mar 28, 2013 at 05:42:23PM +0100, Pali Rohár wrote:
> This patch fixing units (1/10 °C) in which is temperature reported.
>
> Signed-off-by: Pali Rohár
> ---
Applied, thanks!
> drivers/power/rx51_battery.c |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
On Wed, Apr 03, 2013 at 09:31:55AM -0700, Guenter Roeck wrote:
> On Wed, Apr 03, 2013 at 08:18:12PM +0800, Hongbo Zhang wrote:
> > Each of ST-Ericsson X500 chip set series consists of both ABX500 and DBX500
> > chips. This is ABX500 hwmon driver, where the abx500.c is a common layer for
> > all
2013/4/9 :
>
> The patch titled
> Subject: posix_timers: Remove dead task timer expiry caching
> has been added to the -mm tree. Its filename is
> posix_timers-remove-dead-task-timer-expiry-caching.patch
>
> Before you just go and hit "reply", please:
>a) Consider who else should
On Tue, Apr 16, 2013 at 7:52 PM, Tony Lindgren wrote:
> * Roger Quadros [130415 05:44]:
>> On 04/15/2013 03:35 PM, Roger Quadros wrote:
>> > Provide RESET and Power regulators for the USB PHY,
>> > the USB Host port mode and the PHY device.
>> >
>> > Also provide pin multiplexer information for
On 2013/4/17 1:10, Tejun Heo wrote:
> Hello, Li.
>
> On Tue, Apr 16, 2013 at 07:17:17PM +0800, Li Zefan wrote:
> ...
>>> hot-unplug). It currently transfers all its tasks to the nearest
>>> ancestor with executing resources, which is an irreversible process
>>> which would affect all other
Hi Andrew,
This v2 only updates the changelogs to describe more explicitly
the user visible effects as you suggested.
I dropped the 3rd patch for now because it needs more thinking.
Thanks.
Frederic Weisbecker (2):
posix-timers: correctly get dying task time sample in
In order to re-arm a timer after it fired, we take a sample of the
current process or thread cputime.
If the task is dying though, we don't arm anything but we cache the
remaining timer expiration delta for further reads.
Something similar is performed in posix_cpu_timer_get() but here we forget
When a task exits, we perform a caching of the remaining cputime delta
before expiring of its timers.
This is done from the following places:
* When the task is reaped. We iterate through its list of
posix cpu timers and store the remaining timer delta to
the timer struct instead of the
On 04/16/2013 06:24 PM, Borislav Petkov wrote:
> On Tue, Apr 16, 2013 at 08:22:19AM +0800, Alex Shi wrote:
>> testing has a little variation, but the power data is quite accurate.
>> I may change to packing tasks per cpu capacity than current cpu
>> weight. that should has better power efficient
On Wed 17-04-13 08:36:28, Wanpeng Li wrote:
> Changelog:
> * add comments from Andi which indicate shrink gigantic hugetlb page pools
> make
>sense to patchset description.
>
> order >= MAX_ORDER pages are only allocated at boot stage using the
> bootmem allocator with the "hugepages=xxx"
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-twl.c | 16 ++--
1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-twl.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-stmp3xxx.c | 17 -
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-spear.c | 18 --
1 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-spear.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-puv3.c | 27 ---
1 files changed, 12 insertions(+), 15 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-omap.c | 24 ++--
1 files changed, 10 insertions(+), 14 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-coh901331.c | 24 +++-
1 files changed, 11 insertions(+), 13 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-bfin.c | 18 ++
1 files changed, 6 insertions(+), 12 deletions(-)
diff --git a/drivers/rtc/rtc-bfin.c
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/rtc/rtc-at91sam9.c | 23 ++-
1 files changed, 10 insertions(+), 13 deletions(-)
diff --git
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management. Also, use of
pm_message_t is deprecated. Thus, it is removed.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/ili9320.c | 24 +---
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/tosa_bl.c | 18 --
drivers/video/backlight/tosa_lcd.c | 18 --
2 files
Instead of using legacy suspend/resume methods, using newer dev_pm_ops
structure allows better control over power management.
Signed-off-by: Jingoo Han
---
drivers/video/backlight/omap1_bl.c | 22 ++
1 files changed, 10 insertions(+), 12 deletions(-)
diff --git
On Tue, Apr 16, 2013 at 07:27:13PM +0100, David Howells wrote:
> Clean up the use of procfs by the dgrp driver:
>
> (1) Use remove_proc_subtree() for the mass slaughter of a subdir full of proc
> files rather than doing it manually.
>
> (2) When creating files, only call ID_TO_CHAR() once
On Tue, Apr 16, 2013 at 07:26:46PM +0100, David Howells wrote:
> Supply an accessor function for getting the private data from the parent
> proc_dir_entry struct of the proc_dir_entry struct associated with an inode.
>
> ReiserFS, for instance, stores the super_block pointer in the proc directory
On Tue, Apr 16, 2013 at 07:26:39PM +0100, David Howells wrote:
> Don't need to save the PDE of a directory created under /proc/net/rtl8192/ as
> we can use proc subtree deletion to get rid of it and all its children.
>
> Signed-off-by: David Howells
> cc: Jerry Chuang
> cc: Mauro Carvalho
On Tue, Apr 16, 2013 at 07:26:35PM +0100, David Howells wrote:
> Create a dir under /proc/net/r8180/ named for the device and create that
> device's files under there. This means that there won't be a problem for
> multiple devices in the system (if such is possible) and it means we don't
> need
On Tue, Apr 16, 2013 at 07:26:30PM +0100, David Howells wrote:
> Add proc_mkdir_data() to allow procfs directories to be created that are
> annotated at the time of creation with private data rather than doing this
> post-creation. This means no access is then required to the proc_dir_entry
>
On Tue, Apr 16, 2013 at 07:26:26PM +0100, David Howells wrote:
> Move some bits from linux/proc_fs.h to linux/of.h, signal.h and tty.h.
>
> Also move proc_tty_init() and proc_device_tree_init() to fs/proc/internal.h as
> they're internal to procfs.
>
> Signed-off-by: David Howells
> cc:
On Tue, Apr 16, 2013 at 07:25:54PM +0100, David Howells wrote:
> Include missing linux/slab.h inclusions where the source file is currently
> expecting to get kmalloc() and co. through linux/proc_fs.h.
>
> Signed-off-by: David Howells
> cc: linux-s...@vger.kernel.org
> cc:
* Roger Quadros [130415 05:44]:
> On 04/15/2013 03:35 PM, Roger Quadros wrote:
> > Provide RESET and Power regulators for the USB PHY,
> > the USB Host port mode and the PHY device.
> >
> > Also provide pin multiplexer information for USB host
> > pins.
> >
> > This will not work for Rev Cx
On Wed, Apr 17, 2013 at 03:42:03AM +0900, Paul Mundt wrote:
> On Tue, Apr 16, 2013 at 07:28:42AM +0100, Al Viro wrote:
> > On Tue, Apr 16, 2013 at 03:11:13PM +0900, Simon Horman wrote:
> > > On Thu, Apr 11, 2013 at 02:30:09PM +0100, David Howells wrote:
> > > > Don't use create_proc_read_entry()
On 04/16/2013 12:18 PM, Borislav Petkov wrote:
> On Sun, Apr 14, 2013 at 01:03:20PM +0200, Borislav Petkov wrote:
>> On Sun, Apr 14, 2013 at 12:31:12PM +0300, Pekka Enberg wrote:
>>> I obviously support having something like this in mainline. I wonder
>>> though if we could just call this "default
Changelog:
* add comments from Andi which indicate shrink gigantic hugetlb page pools
make
sense to patchset description.
order >= MAX_ORDER pages are only allocated at boot stage using the
bootmem allocator with the "hugepages=xxx" option. These pages are never
free after boot by default
hugetlb_prefault is not used by any users. This patch remove redundant
hugetlb_prefault.
Signed-off-by: Wanpeng Li
---
include/linux/hugetlb.h |2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h
index b7e4106..813b265 100644
---
Use already exist interface huge_page_order() instead of h->order to get
huge page order.
Signed-off-by: Wanpeng Li
---
mm/hugetlb.c | 36 +++-
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 328f140..0cae950
order >= MAX_ORDER pages can't be freed to buddy system directly, this patch
destroy the gigantic hugetlb page to normal order-0 pages and free them one
by one.
Signed-off-by: Wanpeng Li
---
mm/hugetlb.c| 39 +--
mm/internal.h |1 +
Use already exist interface huge_page_shift instead of h->order + PAGE_SHIFT.
Signed-off-by: Wanpeng Li
---
mm/hugetlb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 0cae950..750ed8a 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@
Enable gigantic hugetlb page pools shrinking.
Signed-off-by: Wanpeng Li
---
mm/hugetlb.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index eeaf6f2..328f140 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -1416,7 +1416,8 @@ static
This patch introduces new sysctl knob to support gigantic hugetlb page
pools shrinking. The default value is 0 since gigantic page pools
aren't permitted shrinked by default, administrator can echo 1 to knob
to enable gigantic page pools shrinking after they confirm they won't
use them any more.
On Wed, 17 Apr 2013, Yasuaki Ishimatsu wrote:
> When hot removing memory presented at boot time, following messages are shown:
>
> [ 296.867031] [ cut here ]
> [ 296.922273] kernel BUG at mm/slub.c:3409!
> [ 296.970229] invalid opcode: [#1] SMP
> [ 297.019453]
Hi Matt,
On Tue, Apr 16, 2013 at 11:41 PM, Matt Fleming wrote:
> This patch series introduces the new efivar_entry API, and splits out the
> major
> parts of efivars.c into new files. In particular, having the efivarfs code
> under fs/ allows building an efivarfs.ko module, which means mount(8)
Linus,
Please pull from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git master
To receive the following PPC and ARM KVM fixes
Marc Zyngier (2):
ARM: KVM: fix KVM_CAP_ARM_SET_DEVICE_ADDR reporting
ARM: KVM: fix L_PTE_S2_RDWR to actually be Read/Write
Marcelo Tosatti (1):
Merge
When hot removing memory presented at boot time, following messages are shown:
[ 296.867031] [ cut here ]
[ 296.922273] kernel BUG at mm/slub.c:3409!
[ 296.970229] invalid opcode: [#1] SMP
[ 297.019453] Modules linked in: ebtable_nat ebtables xt_CHECKSUM
On 04/15/2013 12:33:33 PM, Sarah Sharp wrote:
One of the most common frustrations maintainers have with bug
reporters
is the email that starts with "I have a two year old kernel from an
embedded vendor with some random drivers and fixes thrown in, and it's
crashing".
Be specific about what
2013/04/17 0:00, Toshi Kani wrote:
On Tue, 2013-04-16 at 10:10 +0900, Yasuaki Ishimatsu wrote:
When hot removing memory presented at boot time, following messages are shown:
:
The reason why the messages are shown is to release a resource structure,
allocated by bootmem, by kfree(). So
CONFIG_LOCKDEP_SUPPORT is no longer valid.
Singed-off-by: EunBong Song
---
arch/um/defconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/um/defconfig b/arch/um/defconfig
index 08107a7..bbc5aa7 100644
--- a/arch/um/defconfig
+++ b/arch/um/defconfig
@@ -7,7
Oleg Nesterov wrote:
> On 04/16, Michael Neuling wrote:
> >
> > > Benjamin, Paul, arch_dup_task_struct()->flush_ptrace_hw_breakpoint(src)
> > > on powerpc looks "obviously wrong". Don't we need
> > >
> > > - flush_ptrace_hw_breakpoint(src);
> > > + dst->thread->ptrace_bps[0] = NULL;
> >
> >
Hi Rui,
Thank you for your review.
2013/04/16 17:17, Wang, Rui Y wrote:
-Original Message-
From: Yasuaki Ishimatsu
Date: Mon, 15 Apr 2013 11:15:28 +0900
Subject: [Bug fix PATCH] resource: Reusing a resource structure allocated by
bootmem
To: a...@linux-foundation.org
Cc:
Hi Ohad,
On Tue, 16 Apr 2013 20:51:13 +0300 Ohad Ben-Cohen wrote:
>
> On Tue, Apr 16, 2013 at 3:07 AM, Stephen Rothwell
> wrote:
> > On Mon, 15 Apr 2013 09:28:17 +0300 Ohad Ben-Cohen wrote:
> >> Could you please add:
> >>
> >>
On 04/17/2013 04:27 AM, David Rientjes wrote:
> On Fri, 12 Apr 2013, Jiang Liu wrote:
>
>> diff --git a/arch/x86/pci/common.c b/arch/x86/pci/common.c
>> index 901177d..305c68b 100644
>> --- a/arch/x86/pci/common.c
>> +++ b/arch/x86/pci/common.c
>> @@ -6,6 +6,7 @@
>>
>> #include
>> #include
On Tue, Mar 19, 2013 at 10:00:02AM -0500, Kent Yoder wrote:
> Hi Duncan,
>
> On Sun, Mar 17, 2013 at 4:56 PM, Duncan Laurie wrote:
> > If the TPM has already been sent a SaveState command before the driver
> > is loaded it may have problems sending that same command again later.
> >
> > This
Hi Grant,
On Tue, 16 Apr 2013 11:43:36 +0100 grant.lik...@linaro.org wrote:
>
> From: Grant Likely
>
> I've taken a full time position with Linaro and so I'll be using my
> Linaro email address from this point on. It has also been many years
> since I've touched any of the Xilinx related code
On Tue, 26 Mar 2013 11:35:33 -0700 Andrew Morton
wrote:
> Do we need the locking at all? What does it actually do?
>
> sem_lock_and_putref(sma);
> if (sma->sem_perm.deleted) {
> sem_unlock(sma, -1);
>
This is the x86_64 CRC T10 DIF transform accelerated with the PCLMULQDQ
instructions. Details discussing the implementation can be found in the
paper:
"Fast CRC Computation for Generic Polynomials Using PCLMULQDQ Instruction"
URL: http://download.intel.com/design/intarch/papers/323102.pdf
When CRC T10 DIF is calculated using the crypto transform framework, we
wrap the crc_t10dif function call to utilize it. This allows us to
take advantage of any accelerated CRC T10 DIF transform that is
plugged into the crypto framework.
Signed-off-by: Tim Chen
Tested-by: Keith Busch
---
Glue code that plugs the PCLMULQDQ accelerated CRC T10 DIF hash into the
crypto framework. The config CRYPTO_CRCT10DIF_PCLMUL should be turned
on to enable the feature. The crc_t10dif crypto library function will
use this faster algorithm when crct10dif_pclmul module is loaded.
Signed-off-by:
These are simple tests to do sanity check of CRC T10 DIF hash. The
correctness of the transform can be checked with the command
modprobe tcrypt mode=47
The speed of the transform can be evaluated with the command
modprobe tcrypt mode=320
Set the cpu frequency to constant and turn
1 - 100 of 1154 matches
Mail list logo
