There have long been two ways to ask the kernel to create a new
hardlink to the inode represented by an fd: linkat(..., AT_EMPTY_PATH)
and AT_SYMLINK_FOLLOW on /proc/self/fd/N. The latter has no
particular security restrictions, but the former required privilege
until:
commit bb2314b47996491b
On Wed, Aug 21, 2013 at 08:14:46PM +0200, Tibor Billes wrote:
> > From: Paul E. McKenney Sent: 08/20/13 11:43 PM
> > On Tue, Aug 20, 2013 at 10:52:26PM +0200, Tibor Billes wrote:
> > > > From: Paul E. McKenney Sent: 08/20/13 04:53 PM
> > > > On Tue, Aug 20, 2013 at 08:01:28AM +0200, Tibor Billes wr
On Wed, Aug 21, 2013 at 12:03 PM, Cyrill Gorcunov wrote:
> On Wed, Aug 21, 2013 at 08:50:26PM +0200, H. Peter Anvin wrote:
>> But is there a manifest bug or not? What is the deal with Xen?
>>
>
> I personally don't see bug here because
>
> - this swapped page soft dirty bit is set for non-presen
On Wed, 21 Aug 2013 10:08:31 +0200
Jan Kara wrote:
> A CPU can be caught in console_unlock() for a long time (tens of seconds
> are reported by our customers) when other CPUs are using printk heavily
> and serial console makes printing slow. Despite serial console drivers
> are calling touch_nmi_
On Wed, Aug 21, 2013 at 08:50:26PM +0200, H. Peter Anvin wrote:
> But is there a manifest bug or not? What is the deal with Xen?
>
I personally don't see bug here because
- this swapped page soft dirty bit is set for non-present entries only,
never for present ones, just at moment we form s
When freeing a struct radeon_device, its member iio was
not being freed, resulting in a memory leak.
Signed-off-by: Filipe David Borba Manana
---
V2: put kfree() call inside if statement.
drivers/gpu/drm/radeon/radeon_device.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/
On Tuesday 20 August 2013, Sebastian Hesselbarth wrote:
> Perhaps Tegra is the common case but other SoC haven't dug deep enough?
> IMHO from a HW point-of-view clocks are really among the essential
> things that need to be running before you can do anything useful.
>
> Just consider boot loaders
On 08/21, Andy Lutomirski wrote:
>
> On Wed, Aug 21, 2013 at 11:20 AM, Oleg Nesterov wrote:
> > Can't really comment the patch, just a nit:
> >
> > On 08/21, Andy Lutomirski wrote:
> >>
> >> +static bool may_flink(const struct path *path)
> >> +{
> >> + bool ret;
> >> + struct inode *inode
On Tuesday 20 August 2013, Stephen Warren wrote:
> On 08/20/2013 02:44 PM, Arnd Bergmann wrote:
> > On Tuesday 20 August 2013, Stephen Warren wrote:
> Hmm. This probably isn't too hard. I /think/ the only reason the clocks
> are initialized early is:
>
> * The PMC HW block is involved in the path
But is there a manifest bug or not? What is the deal with Xen?
Cyrill Gorcunov wrote:
>On Wed, Aug 21, 2013 at 09:25:47PM +0400, Cyrill Gorcunov wrote:
>> >
>> > However, I do find the use of PTE bits in this way somewhat
>fragile.
>> > What other potential corner cases might still remain that
On Tue, Aug 20, 2013 at 12:24:45PM -0500, Seth Jennings wrote:
> Gah! Forgot the cover letter.
No worries, I barely read them anyway :)
> This patchset just seeks to clean up and refactor some things in
> memory.c for better understanding and possibly better performance due do
> a decrease in mut
On Wed, 21 Aug 2013 10:08:30 +0200
Jan Kara wrote:
> struct irq_work {
> unsigned long flags;
> diff --git a/kernel/irq_work.c b/kernel/irq_work.c
> index 55fcce6..446cd81 100644
> --- a/kernel/irq_work.c
> +++ b/kernel/irq_work.c
> @@ -22,6 +22,9 @@
> static DEFINE_PER_CPU(struct llis
On 08/21/2013 12:30 AM, Sonic Zhang wrote:
> From: Sonic Zhang
>
> The new ADI GPIO2 controller was introduced since the BF548 and BF60x
> processors. It differs a lot from the old one on BF5xx processors. So,
> create a pinctrl driver under the pinctrl framework.
> drivers/pinctrl/Kconfig
On Wed, Aug 21, 2013 at 11:20 AM, Oleg Nesterov wrote:
> Can't really comment the patch, just a nit:
>
> On 08/21, Andy Lutomirski wrote:
>>
>> +static bool may_flink(const struct path *path)
>> +{
>> + bool ret;
>> + struct inode *inode = path->dentry->d_inode;
>> +
>> + /*
>> +
Hi Julius,
Thanks for the patch! Did you test with a USB analyzer to see if the
device was actually going into USB 2.0 Link PM? I'd like to confirm we
really aren't breaking anything for DW3 hosts by enabling this.
Sarah Sharp
On Tue, Aug 20, 2013 at 04:21:49PM -0700, Julius Werner wrote:
> Th
On 08/21, Peter Zijlstra wrote:
>
> OK, so do not remove the MAX_SCHEDULE_TIMEOUT check from
> __schedule_timeout() and change the above to:
>
> static __always_inline long schedule_timeout(long timeout)
> {
> if (__builtin_constant_p(timeout) && timeout == MAX_SCHEDULE_TIMEOUT) {
>
Acked-by: Jeremy Kerr
Tested-by: Jeremy Kerr
Signed-off-by: Dwight Engen
---
arch/powerpc/platforms/cell/spufs/inode.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/cell/spufs/inode.c
b/arch/powerpc/platforms/cell/spufs/inode.c
index f390042
On Wed, Aug 21, 2013 at 11:20 AM, Stephen Warren wrote:
> On 08/20/2013 04:40 PM, Greg KH wrote:
>
> Presumably the idea is that much useful testing only happens on -rc
> kernels rather than linux-next or arbitrary points in Linus' tree.
Linux-next gets little to no testing outside of compiles.
On Fri, 16 Aug 2013, Nicholas A. Bellinger wrote:
> + spinlock_t lock;
Remove the spinlock.
> + unsignednr_free;
> + unsignedfreelist[];
> +};
> +
> +static inline void move_tags(unsigned *dst, unsigned *dst_nr,
> +
On Wed Aug 14 12:43:30 PDT 2013, Sebastian Hesselbarth wrote:
> From: Russell King
>
> This patch adds tda998x specific parameters to allow it to be configured
> for different boards using it. Also, this implements rudimentary audio
> support for S/PDIF attached controllers.
It seems that this p
On Wed, Aug 21, 2013 at 07:09:27PM +0200, Oleg Nesterov wrote:
> So, unlike me, you like -02 more than -Os ;)
I haven't checked the actual flags they enable in a while, but I think I
prefer something in the middle.
Esp. -freorder-blocks and the various -falign flags are something you
really want
When freeing a struct radeon_device, its member iio was
not being freed, resulting in a memory leak.
Signed-off-by: Filipe David Borba Manana
---
drivers/gpu/drm/radeon/radeon_device.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/radeon/radeon_device.c
b/drivers/gpu/dr
On Tue, Aug 20, 2013 at 01:13:30PM +0200, Florian Lobmaier wrote:
> +static bool as3722_readable(struct device *dev, unsigned int reg)
> +{
> + switch (reg) {
> + case AS3722_SD0_VOLTAGE_REG:
> + case AS3722_SD1_VOLTAGE_REG:
If there are no gaps in this a simple if ( >= <= ) would do
On Tue, Aug 20, 2013 at 01:08:00PM +0100, Lee Jones wrote:
> On Tue, 20 Aug 2013, Florian Lobmaier wrote:
> > Signed-off-by: Florian Lobmaier
> > ---
> > drivers/mfd/as3722-regmap.c | 417
> > +++
> > 1 files changed, 417 insertions(+), 0 deletions(-)
>
Can't really comment the patch, just a nit:
On 08/21, Andy Lutomirski wrote:
>
> +static bool may_flink(const struct path *path)
> +{
> + bool ret;
> + struct inode *inode = path->dentry->d_inode;
> +
> + /*
> + * This is racy: I_LINKABLE could be cleared between this check
> +
On Wed, Aug 21, 2013 at 06:42:17PM +0200, Frederic Weisbecker wrote:
> hw_nmi_get_sample_period() is simply a conversion from a period
> to cycles. Lets generalize the API naming so that it can be used for
> wider purpose than just watchdog perf event settings. Also it makes the
> function name les
On Wed Aug 14 12:43:29 PDT 2013, Sebastian Hesselbarth wrote:
> From: Russell King
>
> The video-input-port (VIP) is highly configurable. This prepares
> current driver to allow to configure VIP configuration, as some
> boards connect lcd controller and TDA998x "pin-swapped" and depend
> on VIP t
Hi Benjamin,
> Detecting Win 8 multitouch devices in core allows us to set quirks
> before the device is parsed through hid_hw_start().
> It also simplifies the detection of those devices in hid-multitouch and
> makes the handling of those devices cleaner.
>
> As Win 8 multitouch panels are in th
From: Jesper Dangaard Brouer
Date: Wed, 21 Aug 2013 14:03:50 +0200
>
> On Tue, 20 Aug 2013 08:16:50 -0700
> Greg Kroah-Hartman wrote:
>> On Tue, Aug 20, 2013 at 01:26:29PM +0200, Jesper Dangaard Brouer wrote:
> [...]
>
>> If there are issues with 3.10, that's a different story.
>>
>> > Refac
On 08/20/2013 04:40 PM, Greg KH wrote:
> Hi all,
>
> Given that I had to just revert a patch in the recent stable releases
> that didn't get enough time to "bake" in Linus's tree (or in -next), I
> figured it was worth discussing some possible changes with how "fast" I
> pick up patches for stable
On Wed, Aug 21, 2013 at 09:25:47PM +0400, Cyrill Gorcunov wrote:
> >
> > However, I do find the use of PTE bits in this way somewhat fragile.
> > What other potential corner cases might still remain that will require
> > further games with PTE bits?
>
> OK, so this is not a bug finally. The pro
From: Stephen Rothwell
Date: Wed, 21 Aug 2013 19:10:41 +1000
> Hi all,
>
> After merging the net-next tree, today's linux-next build (i386 defconfig
> and probably others) produced this warning:
>
> net/ipv6/addrconf.c: In function 'addrconf_notify':
> net/ipv6/addrconf.c:2793:22: warning: 'lin
On Tue, Aug 20, 2013 at 09:03:12PM -0400, Josh Boyer wrote:
> Suspend/Resume is broken on a variety of Thinkpad T400 and T500
> machines in 3.10. This was true with 3.10.0 afaik. Current thinking
> is that it's related to the Intel mei/mei_me driver(s). Blacklisting
> those seems to fix things f
Hi Benjamin,
this looks pretty good to me, just a few nitpicks below.
> hid_scan_report() implements its own HID report descriptor parsing. It is
> going to be really bad with the detection of Win 8 certified touchscreen,
> as this detection relies on a special feature and on the report_size and
On Wed, Aug 21, 2013 at 9:10 AM, Stephen Warren wrote:
> On 08/20/2013 08:25 PM, Brian Norris wrote:
>> Hello device tree maintainers,
>>
>> I (sub)maintain the Linux MTD subsystem and hang out on the
>> linux-...@infradead.org mailing list. I have been seeing an increasing
>> number of submission
>
>> > The trivial tree gained conflicts against the crypto, net-next and
>> > wireless trees.
>> >
>> > The aio tree gained conflicts against the aio-direct tree.
>> >
>> > The akpm-current tree gained conflicts against the modules and aio-direct
&
> From: Paul E. McKenney Sent: 08/20/13 11:43 PM
> On Tue, Aug 20, 2013 at 10:52:26PM +0200, Tibor Billes wrote:
> > > From: Paul E. McKenney Sent: 08/20/13 04:53 PM
> > > On Tue, Aug 20, 2013 at 08:01:28AM +0200, Tibor Billes wrote:
> > > > Hi,
> > > >
> > > > I was using the 3.9.7 stable release
There have long been two ways to ask the kernel to create a new
hardlink to the inode represented by an fd: linkat(..., AT_EMPTY_PATH)
and AT_SYMLINK_FOLLOW on /proc/self/fd/N. The latter has no
particular security restrictions, but the former required privilege
until:
commit bb2314b47996491b
On Wed, 21 Aug 2013 19:23:27 +0200
Jochen Striepe wrote:
> ... people are very different. Many just update here and then, but
> there are those who do update on most stable releases. Those are the
> ones you get feedback and testing from, and I think you should encourage
> them to update as soon
From: Ashutosh Dixit
This patch introduces the card "Virtio over PCIe" interface for
Intel MIC. It allows virtio drivers on the card to communicate with their
user space backends on the host via a device page. Ring 3 apps on the host
can add, remove and configure virtio devices. A thin MIC specif
This patch enables the following features:
a) Boots and shuts down the card via sysfs entries.
b) Allocates and maps a device page for communication with the
card driver and updates the device page address via scratchpad
registers.
c) Provides sysfs entries for shutdown status, kernel command
Sincere apologies for the spam. This patches series got sent out 7 times
by mistake due to script bug at my end. I will ensure this never happens
again.
Apologies again.
Sudeep Dutt
On Wed, 2013-08-21 at 10:52 -0700, Sudeep Dutt wrote:
> ChangeLog:
> =
>
> v2 => v3:
> a) Patch 1 data str
From: Dasaratharaman Chandramouli
This patch enables the following features:
a) MSIx, MSI and legacy interrupt support.
b) System Memory Page Table(SMPT) support. SMPT enables system memory
access from the card. On X100 devices the host can program 32 SMPT
registers each capable of accessin
ChangeLog:
=
v2 => v3:
a) Patch 1 data structure cleanups, header file include cleanups,
IDA interface reuse and switching to device_create_with_groups(..)
as per feedback from Greg Kroah-Hartman.
b) Patch 7 signal documentation, sleep workaround removal and sysfs
access API clean
Hi Sudeep,
On Tue, Aug 20, 2013 at 06:08:46PM +0100, Sudeep KarkadaNagesha wrote:
> From: Sudeep KarkadaNagesha
>
> This patch configures the event stream frequency and enables it.
> It also adds the hwcaps as well as compat-specific definitions to
> the user to detect this event stream feature.
This patch does the following:
a) Initializes the Intel MIC X100 platform device and driver.
b) Sets up support to handle shutdown requests from the host.
c) Maps the device page after obtaining the device page address
from the scratchpad registers updated by the host.
d) Informs the host upon a ca
From: Ashutosh Dixit
This patch introduces the host "Virtio over PCIe" interface for
Intel MIC. It allows creating user space backends on the host and instantiating
virtio devices for them on the Intel MIC card. It uses the existing VRINGH
infrastructure in the kernel to access virtio rings from
This patch enables the following:
a) Initializes the Intel MIC X100 PCIe devices.
b) Provides sysfs entries for family and stepping information.
Co-author: Dasaratharaman Chandramouli
Signed-off-by: Ashutosh Dixit
Signed-off-by: Caz Yokoyama
Signed-off-by: Dasaratharaman Chandramouli
Signed-o
On 08/19/2013 01:21 PM, Stephen Warren wrote:
> On 08/17/2013 08:56 AM, Linus Walleij wrote:
>> We currently defer probing of the caller if a pinctrl GPIO
>> request or direction setting comes in before the range mapping
>> a certain GPIO to a certain pin controller is available.
>>
>> This can end
On Wed, 2013-08-21 at 08:53 -0700, Christoph Hellwig wrote:
> On Wed, Aug 21, 2013 at 07:38:21AM -0700, Roland Dreier wrote:
> > I don't understand this. In fact the whole patch series looks quite
> > confused. COMPARE AND WRITE is a normal Data-Out command, with no
> > requirement for special bi
On Wed, 2013-08-21 at 14:32 +, Christoph Lameter wrote:
> On Tue, 20 Aug 2013, Nicholas A. Bellinger wrote:
>
> > On Thu, 2013-08-08 at 14:32 +, Christoph Lameter wrote:
> > > On Wed, 7 Aug 2013, Kent Overstreet wrote:
> > >
> > > > One thing that was bugging me - I was never able to figur
On 08/21/2013 09:19 AM, Lars Poeschel wrote:
> Trivial patch to add Microchip Technology Inc. to the list
> of devicetree vendor prefixes, as it is already used in
> Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
Oh dear. Perhaps it can be legacy-ified...
> diff --git a/Documentation/de
On Wed, 2013-08-21 at 09:14 -0700, Christoph Hellwig wrote:
> I don't like the layering here. The re-execution of the same command
> for both reading and writing the data from/to the backend device already
> looks sketchy here due to doubling work of task attribute handling, the
> various state bi
On 08/21/2013 07:06 AM, George Cherian wrote:
> Hi Stephen,
>
> On 8/20/2013 10:23 PM, Stephen Warren wrote:
>>> >ID pins are connected to pcf8575, and the pcf8575's interrupt line is
>>> >inturn connected to
>>> >gpio bank6 pin 11, we use this gpio interrupt to detect the ID pin
>>> change.
>> In
On 08/21/2013 06:42 AM, Johannes Thumshirn wrote:
> I accidently put the devicetree bindings for the MEN A21 watchdog driver in
> Documentation/devicetree/bindings/gpio instead of
> Documentation/devicetree/bindings/watchdog, this patch addresses this error.
The rename sounds fine, so that part,
A
Hello,
just speaking as a user, not a developer.
On Wed, Aug 21, 2013 at 09:37:13AM -0400, Steven Rostedt wrote:
> First I want to say that I 100% support the idea of waiting at least one
> -rc. Maybe even two.
I think so, too. But ...
> Really, most fixes are for regressions.
[...]
> I
On Wed, Aug 21, 2013 at 6:48 AM, David Vrabel wrote:
> All,
>
> 179ef71c (mm: save soft-dirty bits on swapped pages) introduces a new
> PTE bit on x86 _PTE_SWP_SOFT_DIRTY which has the same value as _PTE_PSE
> and _PTE_PAT.
>
> With a Xen PV guest, the use of the _PTE_PAT will result in the page
>
On 08/21/2013 06:34 AM, Laxman Dewangan wrote:
> Add Palmas pincontrol to Dalmore device tree and make following
> configuration as default:
> - Disable DVFS1 and DVFS2.
> - Set GPIO6 to gpio mode.
> diff --git a/arch/arm/boot/dts/tegra114-dalmore.dts
> b/arch/arm/boot/dts/tegra114-dalmore.dts
>
On Wed, 21 Aug 2013 02:04:17 -0500, Rob Landley wrote:
> On 08/20/2013 10:32:02 PM, Michael Witten wrote:
>
>> On Tue, 20 Aug 2013 19:19:37 -0500, Rob Landley wrote:
>>
>>> Hence asking if we really needed
>>> three separate commits to accomplish something that didn't actually
>>> need to be done
On 08/21/2013 05:23 AM, Laxman Dewangan wrote:
> Add support to pass the config type like GROUP or PIN when using
> the utils or generic pin configuration APIs. This will make the
> APIs more generic.
>
> Added additional inline APIs such that it can be use directly as
> callback for the pinctrl_o
On 08/21/2013 09:42 AM, Frederic Weisbecker wrote:
> With the full dynticks feature and the tricky full system idle
> detection code that is coming soon, it becomes necessary to have
> some debug code that makes sure that the timekeeping is always
> maintained and moving forward as expected.
>
> Th
On Wed, Aug 21, 2013 at 05:56:08PM +0100, David Vrabel wrote:
> >
> > And I asked David to point me how it happens, because I don't
> > understand at which point pse bit get analized when page is
> > not present.
>
> As Jan said, we're concerned that the bit was being used on present PTEs
> and n
On 08/21/2013 07:07:33 AM, Geert Uytterhoeven wrote:
On Wed, Aug 21, 2013 at 10:19 AM, Richard Weinberger
wrote:
> This series is an attempt to remove the SUBARCH make parameter.
> It as introduced at the times of Linux 2.5 for UML to tell the UML
> build system what the real architecture is.
During trinity fuzzing in a kvmtool guest, I stumbled across the
following:
Unable to handle kernel NULL pointer dereference at virtual address 0004
PC is at v9fs_file_do_lock+0xc8/0x1a0
LR is at v9fs_file_do_lock+0x48/0x1a0
[] (v9fs_file_do_lock+0xc8/0x1a0) from []
(locks_remove_flock+0x8c/0
On 08/21/2013 04:48 AM, Laxman Dewangan wrote:
> Palmas rails like LDOs, SMPSs, REGENs, SYSENs can be enable and disable
> by register programming through I2C communication as well as it can be
> enable/disable with the external control input ENABLE1, ENABLE2 and NSLEEP.
>
> Add support for config
On 08/21, Peter Zijlstra wrote:
>
> On Wed, Aug 21, 2013 at 01:35:51PM +0200, Oleg Nesterov wrote:
> >
> > Well, the only overhead is "if(to == MAX_SCHEDULE_TIMEOUT)" at the start.
> > I don't think it makes sense to copy-and-paste the identical code to
> > avoid it. But please ignore, this is real
On 08/21/2013 11:39 AM, Benjamin LaHaise wrote:
> On Wed, Aug 21, 2013 at 11:30:22AM -0500, Dave Kleikamp wrote:
>> Ben,
>> First, let me apologize for neglecting to copy you and linux-aio on the
>> applicable patches. I've been carrying along this patchset, assuming I
>> had gotten the proper cc's
On Wed, Aug 21, 2013 at 04:28:23PM +0100, Mark Brown wrote:
> On Wed, Aug 21, 2013 at 05:08:46PM +0200, David Jander wrote:
>
> > This looks better. Not ideal still, but at least the codec works!
>
> > Should I re-send a patch with this fix?
>
> Yes, it's not the fix we actually want (we want to
On Wed, Aug 21, 2013 at 03:48:52PM +0200, Borislav Petkov wrote:
> On Tue, Aug 20, 2013 at 03:40:32PM -0700, Greg KH wrote:
> > - I will wait for a -rc to come out with the patch in it before putting
> > it into a stable release, unless:
>
> Question: what's the exact reasoning of that delay? To
On Wed, Aug 21, 2013 at 05:22:01PM +0100, Mark Rutland wrote:
> On Wed, Aug 21, 2013 at 04:41:27PM +0100, Guenter Roeck wrote:
> > On Wed, Aug 21, 2013 at 10:14:51AM +0100, Mark Rutland wrote:
> > > On Tue, Aug 20, 2013 at 04:34:56PM +0100, Guenter Roeck wrote:
> > > > On Tue, Aug 20, 2013 at 10:12
On 21/08/13 17:19, Cyrill Gorcunov wrote:
> On Wed, Aug 21, 2013 at 05:03:13PM +0100, Jan Beulich wrote:
>>>
>>> Only to non-present ptes, as far as I know.
>>
>> That's not really any guarantee. And the accessor functions also
>> don't check that they'd be used on non-present PTEs only.
>
> Wait.
The patch removes wakeup related code from
the driver and plaftorm data - it is already
handled by i2c core using I2C_CLIENT_WAKE flag
from struct i2c_board_info. As a result MFD
itself do not requires platform data.
Signed-off-by: Andrzej Hajda
Signed-off-by: Kyungmin Park
---
drivers/mfd/max7
Hi,
The first patch cleans up the driver from unneccesary
wakeup handling.
The second patch adds device tree support to the driver.
Regards
Andrzej
Andrzej Hajda (2):
max77693: remove device wakeup from driver
max77693: added device tree support
drivers/mfd/max77693.c | 18 ++
This patch adds only of_match_table.
There are no device specific properties.
Signed-off-by: Andrzej Hajda
Reviewed-by: Sylwester Nawrocki
Signed-off-by: Kyungmin Park
---
drivers/mfd/max77693.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/mfd/max77693.c b/drivers/mfd/ma
With the full dynticks feature and the tricky full system idle
detection code that is coming soon, it becomes necessary to have
some debug code that makes sure that the timekeeping is always
maintained and moving forward as expected.
This provides a simple detection of missing timekeeping updates
This is going to be used by the timekeeping debugger.
It's a first naive version, at least to make sure that future ad hoc
implementations don't poliferate.
Signed-off-by: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Paul E. McKenney
Cc: John Stultz
Cc: Ste
On 08/21, Peter Zijlstra wrote:
>
> The other consideration is that this adds two branches to the normal
> schedule path. I really don't know what the regular ratio between
> schedule() and io_schedule() is -- and I suspect it can very much depend
> on workload -- but it might be a net loss due to
On Wed, Aug 21, 2013 at 7:38 AM, Roland Dreier wrote:
> I don't understand this. In fact the whole patch series looks quite
> confused. COMPARE AND WRITE is a normal Data-Out command, with no
> requirement for special bidirectional handling or anything like that.
> The only slightly unusual thin
The x86 version of sched_clock() seem to be safely callable
from NMIs, tell about that.
Signed-off-by: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Paul E. McKenney
Cc: John Stultz
Cc: Steven Rostedt
Cc: Don Zickus
---
arch/x86/Kconfig |1 +
1 files c
Add the seqlock version of raw_seqcount_begin() for readers
that can't wait for writers to complete their update and
who can live with seqlock read acquirement failure.
Signed-off-by: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Paul E. McKenney
Cc: John Stul
hw_nmi_get_sample_period() is simply a conversion from a period
to cycles. Lets generalize the API naming so that it can be used for
wider purpose than just watchdog perf event settings. Also it makes the
function name less opaque about what it really does.
Signed-off-by: Frederic Weisbecker
Cc:
sched_clock() should be fast, scalable and not use any lock. As a
resuly it should be safely called from NMIs.
Now just in case there might be some implementation details proper
to some archs that make sched_clock() not reliable or not safe in NMIs,
lets provide a way through Kconfig for archs to
Hi,
With the timekeeping going to be maintained by full system idle detection
patchset from Paul, it seems that the guarantees that enforce timekeeping
progression are going to grow in complexity enough to deserve some automated
checking.
So here is a proposition in the form of a timekeeping watc
Hi,
On Wed, 2013-08-21 at 19:08 +0300, Kirill A. Shutemov wrote:
> Steven Whitehouse wrote:
> > Hi,
> >
> > On Wed, 2013-08-21 at 18:37 +0300, Kirill A. Shutemov wrote:
> > > I've noticed that we allocated unneeded page for cache on read beyond
> > > i_size. Simple test case (I checked it on ramf
On Wed, Aug 21, 2013 at 09:30:03AM -0700, Linus Torvalds wrote:
> On Wed, Aug 21, 2013 at 7:19 AM, Cyrill Gorcunov wrote:
> > On Wed, Aug 21, 2013 at 04:11:25PM +0200, H. Peter Anvin wrote:
> >>
> >> Eep. This should be reverted, indeed. This isn't a manifest bug on !Xen
> >> but we
> >> have g
On 08/20, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> >>
> >> The patch below also needs CLONE_SIGHAND. You can't meaningfully share
> >> signal handlers if you can't represent the pid in the siginfo. pids and
> >> signals are too interconnected.
> >
> > I don't really understand. If
On Wed, Aug 21, 2013 at 11:30:22AM -0500, Dave Kleikamp wrote:
> Ben,
> First, let me apologize for neglecting to copy you and linux-aio on the
> applicable patches. I've been carrying along this patchset, assuming I
> had gotten the proper cc's correct a while back, but I somehow missed
> the aio
Hi,
I'm working on a memory error detector AddressSanitizer for Linux
kernel
(https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel),
it can detect use-after-free and buffer-overflow errors. Currently the
tool is in very early stage and it can contain bugs.
Here is one of th
On 08/21, Kumar Gala wrote:
>
> On Aug 21, 2013, at 1:48 AM, Stephen Boyd wrote:
>
> > The msm serial device bindings were added to the DTS files but
> > never documented. Let's document them now and also fix things up
> > so that it's clearer what hardware is supported. Instead of using
> > hsua
>From f41f64e7f668b86e47059a030cbdcf406c70682c Mon Sep 17 00:00:00 2001
From: Jeffrey Chu
Date: Wed, 21 Aug 2013 09:41:19 -0400
Subject: [PATCH] Add bcm2079x-i2c to drivers/misc
bcm2079x-i2c is the transport driver that supports bcm2079x Controller.
this driver provides basic read(), write(), and
Ben,
First, let me apologize for neglecting to copy you and linux-aio on the
applicable patches. I've been carrying along this patchset, assuming I
had gotten the proper cc's correct a while back, but I somehow missed
the aio pieces.
On 08/21/2013 08:02 AM, Benjamin LaHaise wrote:
> Hello Dave,
>
On Wed, Aug 21, 2013 at 7:19 AM, Cyrill Gorcunov wrote:
> On Wed, Aug 21, 2013 at 04:11:25PM +0200, H. Peter Anvin wrote:
>>
>> Eep. This should be reverted, indeed. This isn't a manifest bug on !Xen
>> but we
>> have gotten requests for WT support which would mean adding in the PAT but
>> aga
On Wed, Aug 21, 2013 at 01:43:07AM -0700, Daniel Gimpelevich wrote:
> There is no need to get an interface specification if we know it's the
> wrong one.
>
> Signed-off-by: Daniel Gimpelevich
Acked-by: Greg Kroah-Hartman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
On Wed, Aug 21, 2013 at 01:43:19AM -0700, Daniel Gimpelevich wrote:
> As Sergei Shtylyov explained in the #mipslinux IRC channel:
> [Mon 2013-08-19 12:28:21 PM PDT] guys, are you sure it's not "DMA
> off stack" case?
> [Mon 2013-08-19 12:28:35 PM PDT] it's a known stack corruptor on
> non-cohe
On Wed, Aug 21, 2013 at 04:41:27PM +0100, Guenter Roeck wrote:
> On Wed, Aug 21, 2013 at 10:14:51AM +0100, Mark Rutland wrote:
> > On Tue, Aug 20, 2013 at 04:34:56PM +0100, Guenter Roeck wrote:
> > > On Tue, Aug 20, 2013 at 10:12:28AM +0100, Mark Rutland wrote:
> > > > Hi Oleksandr,
> > > >
> > >
On 08/21/2013 08:22 AM, Jerome Marchand wrote:
>> > Instead of introducing yet another tunable, why don't we just make the
>> > ratio that comes in from the user more fine-grained?
>> >
>> >sysctl overcommit_ratio=0.2
>> >
>> > We change the internal 'sysctl_overcommit_ratio' to store tenths
Hi Manish,
On Tue, Aug 20, 2013 at 12:25:32PM +0530, Manish Badarkhe wrote:
> Hi Prabhakar,
>
> On Tue, Aug 20, 2013 at 11:44 AM, Prabhakar Lad
> >
> > All the three above properties as per the documentation above
> > are optional, but the code here makes them required property.
> > May be what
On Wed, Aug 21, 2013 at 06:06:02PM +0800, liujunliang_ljl wrote:
> Dear Francois Romieu :
>
> 1, all the format problems have been fixed
>
> 2, sr9700.h registers definition is re-written
>
> 3, Thanks for your detail checking and I have beed
> scripts/checkpatch.pl the
On Wed, Aug 21, 2013 at 05:03:13PM +0100, Jan Beulich wrote:
> >
> > Only to non-present ptes, as far as I know.
>
> That's not really any guarantee. And the accessor functions also
> don't check that they'd be used on non-present PTEs only.
Wait. This _PAGE_SWP_SOFT_DIRTY bit (which is in real
On Wed, Aug 21, 2013 at 05:49:58PM +0800, Li Zhong wrote:
> DEBUG_KOBJECT_RELEASE helps to find the issue attached below.
>
> After some investigation, it seems the reason is:
> The mod->mkobj.kobj(a01600d0 below) is freed together with mod
> itself in free_module(). However, its children
301 - 400 of 760 matches
Mail list logo
