Hi Vineet,
On Mon, 28 Jan 2013 12:40:24 +0530 Vineet Gupta
wrote:
>
> Stephen, can you please add the following branch (rebased off 3.8-rc5) to
> linux-next
>
> git://github.com/foss-for-synopsys-dwc-arc-processors/linux.git arc-next
Added from today (though there may not be a linux-next
From: "Michael S. Tsirkin"
Date: Mon, 28 Jan 2013 12:38:02 +0200
> Commit c8d68e6be1c3b242f1c598595830890b65cea64a removed carrier off call
> from tun_detach since it's now called on queue disable and not only on
> tun close. This confuses userspace which used this flag to detect a
> free tun.
Le mardi 29 janvier 2013 18:59:12, Jason Gunthorpe a écrit :
> On Tue, Jan 29, 2013 at 04:24:07PM +0100, Florian Fainelli wrote:
> > - dev->err_interrupt = irq_of_parse_and_map(pdev->dev.of_node, 0);
> > + if (pdev->dev.of_node) {
> > + dev->regs = of_iomap(pdev->dev.of_node, 0);
> >
Le mardi 29 janvier 2013 19:13:06, Jason Gunthorpe a écrit :
> On Tue, Jan 29, 2013 at 04:24:08PM +0100, Florian Fainelli wrote:
> > This patch converts the Marvell MV643XX ethernet driver to use the
> > Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
> > registering the Marvell
On Mon, Jan 28, 2013 at 03:49:22PM -0600, Seth Jennings wrote:
> debugfs currently lack the ability to create attributes
> that set/get atomic_t values.
>
> This patch adds support for this through a new
> debugfs_create_atomic_t() function.
>
> Signed-off-by: Seth Jennings
> Acked-by: Greg
Am 29.01.2013 16:51, schrieb Alexander Holler:
Am 29.01.2013 12:11, schrieb Alexander Holler:
To explain the problem on shutdown a bit further, I think the following
happens (usb and driver are statically linked and started by the kernel):
shutdown -> kill signal -> usb stack shuts down ->
Hey,
Generally looks good to me although I haven't really delved into the
behavior (you're gonna be there for the fallouts, right?). Just some
minor comments.
> +static int propagate_behavior(struct dev_cgroup *devcg_root)
> +{
> + struct cgroup *root = devcg_root->css.cgroup, *pos;
> +
Hi,
this is rc5 + tip/master from 2 days ago, when resuming I get this fun
message:
...
[15117.684975] Restarting tasks ... done.
[15117.687201] video LNXVIDEO:00: Restoring backlight state
[15117.720469] ehci-pci :00:1d.0: power state changed by ACPI to D3cold
[15117.721414] ehci-pci
> -Original Message-
> From: Shuah Khan [mailto:shuahk...@gmail.com]
> Sent: Tuesday, January 29, 2013 2:11 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
> wrote:
> >>
On 1/29/13 12:49 PM, Ben Hutchings wrote:
On Fri, 2013-01-25 at 13:31 -0500, Valdis Kletnieks wrote:
[...]
it's a zero-hit thing for people who don't choose to configure
it into their kernel.
[...]
People with high-overhead changes always say this, but before long
distributions will be
On Tue, Jan 29, 2013 at 03:01:13PM -0500, Mimi Zohar wrote:
[..]
> > Hi Mimi,
> >
> > Can we add another field to ima_rule_entry, say .enforcement to control
> > the behavior of .action. Possible values of .enforcement could be, say.
> >
> > ALL
> > SIGNED_ONLY
> >
> > ALL will be default. And
On Tue, 2013-01-29 at 13:20 -0500, Vivek Goyal wrote:
> On Mon, Jan 28, 2013 at 08:48:55PM -0500, Mimi Zohar wrote:
>
> [..]
> > > Hi Mimi,
> > >
> > > By policy you mean ima rules here? So I can either enable default rules
> > > (tcb default rules for appraisal and measurement) by using kernel
Hello, Kent.
On Tue, Jan 29, 2013 at 11:51:41AM -0800, Kent Overstreet wrote:
> > What about overflow? Note that we can have systemetic cases where ref
> > is gotten on one cpu and put on another transferring counts in a
> > specific direction.
>
> Heh, this keeps coming up.
>
> It works
Hi,
Please find the latest report on new defect(s) that have been introduced to the
Linux Kernel found with Coverity SCAN.
Defect(s) Reported-by: Coverity Scan:
___
** CID 967920: Allocation too small for type (SIZECHECK)
On Tue, Jan 29, 2013 at 02:08:07PM -0500, a...@redhat.com wrote:
> This patch is in preparation for hierarchy support.
Ditto.
> Cc: Tejun Heo
> Cc: Serge Hallyn
> Signed-off-by: Aristeu Rozanski
Acked-by: Tejun Heo
Thanks.
--
tejun
--
To unsubscribe from this list: send the line
On Tue, Jan 29, 2013 at 02:08:06PM -0500, a...@redhat.com wrote:
> This patch is in preparation for hierarchy support
It would be nice to note this is purely organizational and doesn't
make any functional changes.
> Cc: Tejun Heo
> Cc: Serge Hallyn
> Signed-off-by: Aristeu Rozanski
Acked-by:
On Tue, Jan 29, 2013 at 02:08:05PM -0500, a...@redhat.com wrote:
> Allocate resources and change behavior only when online.
> This patch is in preparation for hierarchy support.
I think the description is a bit lacking. We need this because we
need to reliably determine whether a certain node is
On Tue, Jan 29, 2013 at 11:29:04AM -0800, Tejun Heo wrote:
> Hey, Kent.
>
> On Tue, Jan 29, 2013 at 08:39:42AM -0800, Kent Overstreet wrote:
> > Oh, if this is going to be widely used I should probably have a
> > different implementation for archs that don't have atomic64_t in
> > hardware. Don't
On 01/29, Jiri Slaby wrote:
>
> On 01/29/2013 08:07 PM, Oleg Nesterov wrote:
> >
> > Change set_termios/set_termiox to return -ERESTARTSYS to fix this
> > particular problem.
>
> This looks reasonable. However given the link above says:
> You are not authorized to access bug #904907.
> the
On Tue, Jan 29, 2013 at 02:08:04PM -0500, a...@redhat.com wrote:
> Currently may_access() is only able to verify if an exception is valid for the
> current cgroup, which has the same behavior. With hierarchy, it'll be also
> used
> to verify if a cgroup local exception is valid towards its cgroup
On Tue, Jan 29, 2013 at 02:08:03PM -0500, a...@redhat.com wrote:
> In order to make the next patch more clear, expand may_access() logic.
>
> Cc: Tejun Heo
> Cc: Serge Hallyn
> Signed-off-by: Aristeu Rozanski
Maybe convert the function to return bool while at it?
Acked-by: Tejun Heo
--
On Tue, Jan 29, 2013 at 02:08:02PM -0500, a...@redhat.com wrote:
> In preparation for better hierarchy support, it's needed to retain the local
> settings in order to try to reapply them after a propagated change if they're
> still valid.
>
> v2: split this patch in two, one to just move
On Tue, Jan 29, 2013 at 11:41:55AM -0800, Tejun Heo wrote:
> On Tue, Jan 29, 2013 at 02:08:00PM -0500, a...@redhat.com wrote:
> > In the following patches, device_cgroup structure will have two sets of
> > behavior and exceptions list (actual one, another with the local settings)
> > so rework the
On Tue, Jan 29, 2013 at 02:08:01PM -0500, a...@redhat.com wrote:
> In preparation for the next patch, reorder dev_exception_add() and
> dev_exception_rm().
It would be nice to have something like "this change doesn't introduce
any functional changes".
> Cc: Tejun Heo
> Cc: Serge Hallyn
>
On Tue, Jan 29, 2013 at 02:08:00PM -0500, a...@redhat.com wrote:
> In the following patches, device_cgroup structure will have two sets of
> behavior and exceptions list (actual one, another with the local settings)
> so rework the functions to use exception list, not a device_cgroup.
>
> Cc:
On Mon, Jan 28, 2013 at 8:22 PM, Yinghai Lu wrote:
> On Mon, Jan 28, 2013 at 7:50 PM, Yinghai Lu wrote:
>> On Sun, Jan 27, 2013 at 7:36 PM, H. Peter Anvin wrote:
>> Did you get chance to put them into for-x86-boot?
>>
>> You need to skip the first two about memmap= exactmap and reserveram ...
On 01/29/2013 08:07 PM, Oleg Nesterov wrote:
> See https://bugzilla.redhat.com/show_bug.cgi?id=904907
> read command causes bash to abort with double free or corruption (out).
>
> A simple test-case from Roman:
>
> // Compile the reproducer and send sigchld ti that process.
> //
Hey, Kent.
On Tue, Jan 29, 2013 at 08:39:42AM -0800, Kent Overstreet wrote:
> Oh, if this is going to be widely used I should probably have a
> different implementation for archs that don't have atomic64_t in
> hardware. Don't suppose you know the CONFIG_ macro to test against? I
> couldn't find
On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
wrote:
>> -Original Message-
>> I was out sick for a few days and finally picked this bisect backup
>> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
>> and also did bisect at drivers/gpu/drm/radeon instead. Here
This patch makes all changes propagate down in hierarchy respecting when
possible local configurations.
Behavior changes will clean up exceptions in all the children except when the
parent changes the behavior from allow to deny and the child's behavior was
already deny, in which case the local
In preparation for the next patch, reorder dev_exception_add() and
dev_exception_rm().
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
security/device_cgroup.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
---
This patch is in preparation for hierarchy support.
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
security/device_cgroup.c | 34 --
1 file changed, 16 insertions(+), 18 deletions(-)
--- github.orig/security/device_cgroup.c
In the following patches, device_cgroup structure will have two sets of
behavior and exceptions list (actual one, another with the local settings)
so rework the functions to use exception list, not a device_cgroup.
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
See https://bugzilla.redhat.com/show_bug.cgi?id=904907
read command causes bash to abort with double free or corruption (out).
A simple test-case from Roman:
// Compile the reproducer and send sigchld ti that process.
// EINTR occurs even if SA_RESTART flag is set.
void
Hello.
The patch looks really trivial and I even cc'ed -stable.
But it needs the review from someone who understands the drivers/tty
code, perhaps there is a reason why we should not restart TCGETA/etc.
I do not even know what set_termios() actually does ;)
Oleg.
--
To unsubscribe from this
In preparation for better hierarchy support, it's needed to retain the local
settings in order to try to reapply them after a propagated change if they're
still valid.
v2: split this patch in two, one to just move dev_exception_rm() before
dev_exception_add() while keeping functional changes
This patchset implements device cgroup hierarchy. Behaviors and exceptions
will be propagated down in the tree and local preferences will be re-evaluated
everytime a change in its parent occours, reapplying them if it's still
possible.
git://github.com/aristeu/linux-2.6.git
branch:
This patch is in preparation for hierarchy support
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
security/device_cgroup.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
--- github.orig/security/device_cgroup.c2013-01-29
Allocate resources and change behavior only when online.
This patch is in preparation for hierarchy support.
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
security/device_cgroup.c | 59 +--
1 file changed, 42 insertions(+),
Currently may_access() is only able to verify if an exception is valid for the
current cgroup, which has the same behavior. With hierarchy, it'll be also used
to verify if a cgroup local exception is valid towards its cgroup parent, which
might have different behavior.
v2:
- updated patch
In order to make the next patch more clear, expand may_access() logic.
Cc: Tejun Heo
Cc: Serge Hallyn
Signed-off-by: Aristeu Rozanski
---
security/device_cgroup.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
--- github.orig/security/device_cgroup.c
If signalfd is created with the flag SFD_PEEK, it reads siginfo-s
without dequeuing signals.
For reading not first siginfo pread(fd, buf, size, pos) can be used,
where ppos / sizeof(signalfd_siginfo) is a sequence number of a signal
in a queue.
This functionality is required for checkpointing
Hi guys,
The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:
Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git
for you to fetch changes up to
From: Stephen Warren
of_regulator_match() saves some dynamcially allocated state into the
match table that's passed to it. By implementation and not contract, for
each match table entry, if non-NULL state is already present,
of_regulator_match() will not overwrite it. of_regulator_match() is
On Tue, Jan 29, 2013 at 10:51:18AM -0800, Simon Que wrote:
> Add a config option "ERROR_ON_WARNING" that adds the "-Werror" flag to
> gcc, which turns warnings into errors.
>
> This option enables developers to set a stricter level of code checking
> for kernel code: all code must be
On 01/29/2013 12:27 AM, Minchan Kim wrote:
> On Mon, Jan 28, 2013 at 03:49:26PM -0600, Seth Jennings wrote:
>> +/*
>> +* tunables
>> +**/
>> +/* Enable/disable zswap (enabled by default, fixed at boot for now) */
>> +static bool
Add a config option "ERROR_ON_WARNING" that adds the "-Werror" flag to
gcc, which turns warnings into errors.
This option enables developers to set a stricter level of code checking
for kernel code: all code must be warning-free.
Signed-off-by: Simon Que
Signed-off-by: Mandeep Singh Baines
---
From: Ben Hutchings
Date: Tue, 29 Jan 2013 17:49:15 +
> On Fri, 2013-01-25 at 13:31 -0500, Valdis Kletnieks wrote:
> [...]
>> it's a zero-hit thing for people who don't choose to configure
>> it into their kernel.
> [...]
>
> People with high-overhead changes always say this, but before
On Tue, Jan 29, 2013 at 10:16 AM, Linus Walleij
wrote:
> On Tue, Jan 29, 2013 at 12:00 AM, Olof Johansson wrote:
>> On Mon, Jan 28, 2013 at 02:52:31PM +0100, Linus Walleij wrote:
>>> From: Linus Walleij
>>>
>>> The pin controller is an inherent part of the SoC, without
>>> it the system will
On 01/28/2013 08:39 PM, Mark Brown wrote:
> On Mon, Jan 28, 2013 at 05:03:29PM -0700, Stephen Warren wrote:
>> On 01/23/2013 07:31 PM, Axel Lin wrote:
>>> The dev parameter is the device requesting the data. In this
>>> case it should be >dev rather than pdev->dev.parent.
>
>>> The dev parameter
On 01/29/2013 12:42 PM, Jeff Moyer wrote:
> Dave Kleikamp writes:
>
>> Al,
>> I'd like to push this patchset to linux-next. Would you like to pull it
>> into your vfs tree, would you rather I submitted it separately, or do
>> you have any issues with it before including it?
>
> I'm still
On 01/28/2013 10:43 PM, Santosh Shilimkar wrote:
Jon,
On Tuesday 29 January 2013 05:31 AM, John Stultz wrote:
On 01/27/2013 10:08 PM, Santosh Shilimkar wrote:
On Tuesday 22 January 2013 08:35 PM, Santosh Shilimkar wrote:
On Tuesday 22 January 2013 08:21 PM, Russell King - ARM Linux wrote:
Dave Kleikamp writes:
> Al,
> I'd like to push this patchset to linux-next. Would you like to pull it
> into your vfs tree, would you rather I submitted it separately, or do
> you have any issues with it before including it?
I'm still chasing one regression in this patchset. If you use the
On Tue, Jan 29, 2013 at 10:48:00AM +0200, Kasatkin, Dmitry wrote:
> On Mon, Jan 28, 2013 at 8:52 PM, Vivek Goyal wrote:
> > On Mon, Jan 28, 2013 at 05:20:20PM +0200, Kasatkin, Dmitry wrote:
> >
> > [..]
> >> > Ok. I am hoping that it will be more than the kernel command line we
> >> > support. In
The following rule looks promising:
@r@
constant c;
identifier i;
expression e;
@@
(
e | c@i
|
e & c@i
|
e |= c@i
|
e &= c@i
)
@@
constant r.c,c1;
identifier i1;
expression e;
@@
*c1@i1 + c
That is, the sum of two constants where at least one of them has been used
with & or |.
julia
--
To
On Mon, Jan 28, 2013 at 08:48:55PM -0500, Mimi Zohar wrote:
[..]
> > Hi Mimi,
> >
> > By policy you mean ima rules here? So I can either enable default rules
> > (tcb default rules for appraisal and measurement) by using kernel command
> > line options or dynamically configure my own rules using
On Tue, Jan 29, 2013 at 12:00 AM, Olof Johansson wrote:
> On Mon, Jan 28, 2013 at 02:52:31PM +0100, Linus Walleij wrote:
>> From: Linus Walleij
>>
>> The pin controller is an inherent part of the SoC, without
>> it the system will not boot, thus it needs to be selected
>> from Kconfig.
>>
>> Cc:
On Tue, Jan 29, 2013 at 04:24:08PM +0100, Florian Fainelli wrote:
> This patch converts the Marvell MV643XX ethernet driver to use the
> Marvell Orion MDIO driver. As a result, PowerPC and ARM platforms
> registering the Marvell MV643XX ethernet driver are also updated to
> register a Marvell
On Tue, Jan 29, 2013 at 05:55:54PM +, Woodhouse, David wrote:
> That's different though. That's because GCC didn't have a generic
> __builtin_bswap16() until 4.8, while PowerPC got it in 4.6.
>
> That's a relatively simple and manageable one-off arch-dependency. But
> once we get into a mass
On 01/29/2013 05:56 AM, Laxman Dewangan wrote:
> Add APB DMA requestor and serial aliases for serial controller.
> There will be two serial driver i.e. 8250 based simple serial driver
> and APB DMA based serial driver for higher baudrate and performace.
>
> The simple serial driver get enabled
Dan Williams writes:
> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
>> From: danielepa
>>
>> Add PID and special handling for Telit LE920
>
> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
> interface that could be used instead of PPP? What's the lsusb -v
On Tue, 2013-01-29 at 11:57 -0600, Clark Williams wrote:
> > > +/* provide a home for sysctl scheduler tuning knobs */
> > > +
> > > +/*
> > > + * default timeslice is 100 msecs (used only for SCHED_RR tasks).
> > > + * Timeslices get refilled after they expire.
> > > + */
> > > +#define
I started screwing aronud just to see how hard a conversion would be and
what it'd look like. I _think_ this is complete, but there's enough
going on I undoubtedly missed something.
Completely untested - builds and that's it. I'm sure it's broken.
Deletes almost 100 lines of code though. I like
On Tue, 2013-01-29 at 18:49 +0100, Julia Lawall wrote:
> How about the following (from today's linux-next). They appear to be
> trying to do the same calculation, once with + and once with |.
(cc'ing the original developer and Russell King)
Likely the it8152_pci_platform_notify uses should use
On Tue, Jan 29, 2013 at 04:24:07PM +0100, Florian Fainelli wrote:
> - dev->err_interrupt = irq_of_parse_and_map(pdev->dev.of_node, 0);
> + if (pdev->dev.of_node) {
> + dev->regs = of_iomap(pdev->dev.of_node, 0);
> + if (!dev->regs) {
> +
On Tue, 29 Jan 2013 15:05:43 +0900
Namhyung Kim wrote:
> Hi Clark,
>
> On Mon, 28 Jan 2013 14:31:20 -0600, Clark Williams wrote:
> > Move all the scheduler sysctl-related bits out of include/linux/sched.h
> > into a new file include/linux/sched_sysctl.h.
> >
> > Signed-off-by: Clark Williams
>
On Tue, 29 Jan 2013 09:12:45 +0800
Li Zefan wrote:
> > -extern void sched_autogroup_create_attach(struct task_struct *p);
> > -extern void sched_autogroup_detach(struct task_struct *p);
> > -extern void sched_autogroup_fork(struct signal_struct *sig);
> > -extern void sched_autogroup_exit(struct
On Tue, 2013-01-29 at 18:42 +0100, Borislav Petkov wrote:
> On Tue, Jan 29, 2013 at 04:46:58PM +, Woodhouse, David wrote:
> > If we're really going to have many different architectures depending
> > on different versions of GCC for this (if it wasn't sane to use
> > it from 4.4/4.8 when it got
On Tue, 2013-01-29 at 17:52 +0100, Maarten Lankhorst wrote:
> It looks like the original commit that copied the rom contents from efi
> always copied
> the rom, and the fixup in setup_efi_pci from commit 886d751a2ea99a160
> ("x86, efi: correct precedence of operators in setup_efi_pci") broke
On Tue, Jan 29, 2013 at 07:15:07PM +0530, Vineet Gupta wrote:
> On Tuesday 29 January 2013 12:14 AM, Sam Ravnborg wrote:
> > On Mon, Jan 28, 2013 at 11:59:36AM +0530, Vineet Gupta wrote:
> >> Hi Sam,
> >>
> >> On Thursday 24 January 2013 04:20 PM, Vineet Gupta wrote:
> >>> Arnd in his review
On Fri, 2013-01-25 at 13:31 -0500, Valdis Kletnieks wrote:
[...]
> it's a zero-hit thing for people who don't choose to configure
> it into their kernel.
[...]
People with high-overhead changes always say this, but before long
distributions will be expected to enable it and then everyone pays the
How about the following (from today's linux-next). They appear to be
trying to do the same calculation, once with + and once with |.
arch/arm/common/it8152.c
int dma_set_coherent_mask(struct device *dev, u64 mask)
{
if (mask >= PHYS_OFFSET + SZ_64M - 1)
return 0;
On Tue, 2013-01-29 at 11:19 -0600, Dan Williams wrote:
> On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> > From: danielepa
> >
> > Add PID and special handling for Telit LE920
>
> Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
> interface that could be used
Here are the warnings for yesterday's linux-next (next-20130128).
regards,
dan carpenter
arch/x86/crypto/crc32-pclmul_glue.c:66 crc32_pclmul_le() warn: bit mask
'SCALE_F_MASK' used for math 'p + (16 - 1)'
arch/x86/kernel/cpu/mcheck/mce_amd.c:155 threshold_restart_bank() warn: bit
mask
On Tue, Jan 29, 2013 at 04:46:58PM +, Woodhouse, David wrote:
> If we're really going to have many different architectures depending
> on different versions of GCC for this (if it wasn't sane to use
> it from 4.4/4.8 when it got introduced, and depends on some later
> arch-specific
On 01/29/2013 05:56 AM, Laxman Dewangan wrote:
> NVIDIA's Tegra114 has 32 channels APB DMA controller. Add DT entry for
> APB DMA controllers and make it compatible with "nvidia,tegra114-apbdma".
The APB DMA controller node needs a clocks property. The same goes for
I2C and KBC. I'd like to avoid
On 01/29/2013 12:27 AM, Minchan Kim wrote:
> First feeling is it's simple and nice approach.
> Although we have some problems to decide policy, it could solve by later patch
> so I hope we make basic infrasture more solid by lots of comment.
Thanks very much for the review!
>
> There are two
On Mon, 2013-01-28 at 16:47 +0100, Daniele Palmas wrote:
> From: danielepa
>
> Add PID and special handling for Telit LE920
Any idea what interfaces 1 and 5 are? Is one perhaps a pseudo-ethernet
interface that could be used instead of PPP? What's the lsusb -v output
for the device?
Dan
>
On Tue, 2013-01-29 at 10:33 -0500, Don Zickus wrote:
> Hi Mike,
>
> On Tue, Jan 29, 2013 at 05:42:43PM +0400, Mike Lykov wrote:
> >
> > So my questions:
> >
> > 1. Are there a BUG in soft lockup detection mechanizm? Changing
> > watchdog_thresh to 30 have a side effect in production - D-state
>
On Tue, 2013-01-29 at 17:55 +0100, Frederic Weisbecker wrote:
>
> > Perhaps the best thing to do is to have the irq vtime determine usermode
> > or not with "user_mode(get_irq_regs())". I'll try it.
>
> That will get rid of those few microsecond error margin but I bet
> that's not where the
Hi Vineet,
On 24/01/13 11:06, Vineet Gupta wrote:
> Signed-off-by: Vineet Gupta
> Cc: Robert Richter
> Cc: oprofile-l...@lists.sf.net
> ---
> arch/arc/Kconfig |1 +
> arch/arc/Makefile |2 ++
> arch/arc/oprofile/Makefile |9 +
> arch/arc/oprofile/common.c
The patch ae926051d7eb: "staging: ozwpan: Added USB HCD
implementation" from Feb 20, 2012, leads to the following warning:
drivers/staging/ozwpan/ozhcd.c:1094 oz_hcd_heartbeat()
warn: what is this condition about? 'ep->buffered_units * 50'
Reported-by: Dan Carpenter
Signed-off-by:
On Tue, 29 Jan 2013, Stefan Richter wrote:
> Added Cc: linux-pm.
>
> On Jan 29 Mark Einon wrote:
> > On 28 January 2013 23:01, Stefan Richter wrote:
> > > On Jan 28 Mark Einon wrote:
> > >> This patch fixes the kernel warning generated when putting an MSI MS-1727
> > >> GT740 laptop into
On Mon, Jan 28, 2013 at 08:48:55PM -0500, Mimi Zohar wrote:
[..]
> > Also given the fact that we allow loading policy from initramfs, root
> > can rebuild initramfs and change the policy which takes effect over next
> > reboot. So in priciple this works only when we are trying to impose some
> >
2013/1/29 Steven Rostedt :
> On Tue, 2013-01-29 at 16:12 +0100, Frederic Weisbecker wrote:
>
>> I have set some cputime tracepoint and looked at the stacktrace. They
>> are sorted by weight, which is the amount of cputime accounted. I
>> can't find anything wrong on these. See attachment.
>
>
It looks like the original commit that copied the rom contents from efi always
copied
the rom, and the fixup in setup_efi_pci from commit 886d751a2ea99a160
("x86, efi: correct precedence of operators in setup_efi_pci") broke that.
This resulted in macbook pro's no longer finding the rom images,
Hi everyone,
On Tue, Jan 29, 2013 at 04:26:13AM +0200, Izik Eidus wrote:
> On 01/29/2013 02:49 AM, Izik Eidus wrote:
> > On 01/29/2013 01:54 AM, Andrew Morton wrote:
> >> On Fri, 25 Jan 2013 17:53:10 -0800 (PST)
> >> Hugh Dickins wrote:
> >>
> >>> Here's a KSM series
> >> Sanity check: do you
On Tue, 2013-01-29 at 09:35 +0100, Borislav Petkov wrote:
>
> >
> > #ifdef CONFIG_ARCH_USE_BUILTIN_BSWAP
> > -#if GCC_VERSION >= 40400
> > +#if (!defined(__arm__) && GCC_VERSION >= 40400) || \
> > +(defined(__arm__) && GCC_VERSION >= 40600)
>
> There should be no arch-specific stuff in a
On Tue, 2013-01-29 at 16:12 +0100, Frederic Weisbecker wrote:
> I have set some cputime tracepoint and looked at the stacktrace. They
> are sorted by weight, which is the amount of cputime accounted. I
> can't find anything wrong on these. See attachment.
That's because a histogram doesn't show
Dear Florian Fainelli,
On Tue, 29 Jan 2013 17:27:56 +0100, Florian Fainelli wrote:
> It looks like I introduced two redundant mvmdio instances as ge01
> refers to the ge00 smi bus (the same applies to ge11 and ge10).
> Thanks for spotting this.
Ok, good.
> If you take a closer look at
Hi Mark,
As requested, the whole-shebang.
The Mainline AB8500 and DB8500 regulators are currently stuck in the
Victorian era (AKA v2.6.35). This branch contains all of the
upstreamable changes that have occurred on the internal repository and
aims to bring them back into the 20th century.
If
On Mon, Jan 28, 2013 at 01:50:42PM -0800, Tejun Heo wrote:
> Hello, Kent.
>
> On Mon, Jan 28, 2013 at 01:45:06PM -0800, Kent Overstreet wrote:
> > Ahh. Bias value sounds... hacky (i.e. harder to convince myself it's
> > correct) but I see what you're getting at.
>
> I don't think it's that
On 01/29/2013 02:51 AM, Peter De Schrijver wrote:
> On Mon, Jan 28, 2013 at 05:49:53PM +0100, Stephen Warren wrote:
>> On 01/28/2013 08:54 AM, Peter De Schrijver wrote:
>>> The tegra peripheral clock type uses struct clk_mux directly, so it needs to
>>> be updated to handle the new mask and table
On Sun, Jan 27, 2013 at 05:40:00PM +0100, Emil Goode wrote:
> The function pointer x2apic_available in struct hypervisor_x86 is
> supposed to point to functions that return bool. This patch changes
> the return type of the kvm_para_available function to bool.
>
> Sparse warnings:
>
>
On Mon, Jan 28, 2013 at 07:14:02PM -0500, Mimi Zohar wrote:
[..]
> The 'trusted' keyring is a solution for installing only distro or third
> party signed packages. How would a developer, for instance, create,
> sign, and install his own package and add his public key safely?
Hi Mimi,
I guess
From: Zach Brown
This moves the iov_iter functions in to their own file. We're going to
be working on them in upcoming patches. They become sufficiently large,
and remain self-contained, to justify seperating them from the rest of
the huge mm/filemap.c.
Signed-off-by: Dave Kleikamp
Acked-by:
From: Zach Brown
The generic direct write path wants to shorten its memory vector. It
does this when it finds that it has to perform a partial write due to
LIMIT_FSIZE. .direct_IO() always performs IO on all of the referenced
memory because it doesn't have an argument to specify the length of
Signed-off-by: Dave Kleikamp
---
fs/iov-iter.c | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/fs/iov-iter.c b/fs/iov-iter.c
index 83f7594..5c4f3a5 100644
--- a/fs/iov-iter.c
+++ b/fs/iov-iter.c
@@ -6,8 +6,8 @@
#include
#include
-static size_t
From: Zach Brown
This uses the new kernel aio interface to process loopback IO by
submitting concurrent direct aio. Previously loop's IO was serialized
by synchronous processing in a thread.
The aio operations specify the memory for the IO with the bio_vec arrays
directly instead of mappings
On Tue, 2013-01-29 at 17:19 +0100, Julia Lawall wrote:
> > On Tue, 2013-01-29 at 10:55 -0500, valdis.kletni...@vt.edu wrote:
[]
> > > I wonder if there's a way to write a coccinelle patch to find places
> > > where we do arithmetic operations on bitmasks
[]
> If the definition of a bitmask is
301 - 400 of 1454 matches
Mail list logo