Convert file->f_dentry->d_inode to file_inode() so as to get layered
filesystems right.
Found with: git grep '[.>]f_dentry'
Signed-off-by: David Howells
---
arch/cris/arch-v32/drivers/sync_serial.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch provides an implementation of irq_set_nmi_routing by
allowing SPIs to be switched between group 1 (IRQ) and group 0 (FIQ).
It also repaces the interface used between the default FIQ handler and
the GIC. These extensions are required in order to allow SPIs to be
acknowledged and
armv7pmu_disable_event() is called during irq handler. If irq handling
switches over to fiq then the spin locks in this function risks deadlock.
Both armv7_pmnc_disable_counter() and armv7_pmnc_disable_intens() are
unconditional co-processor writes. I haven't yet come up with an
schedule where
Extends the irq statistics for ARM, making it possible to quickly
observe how many times the default FIQ handler has executed.
In /proc/interrupts we use the NMI terminology (rather than FIQ) because
the statistic is only likely to be updated when we run the default FIQ
handler
Some combinations of architectures and interrupt controllers make it
possible for abitrary interrupt signals to be selectively made immune to
masking by local_irq_disable(). For example, on ARM platforms, many
interrupt controllers allow interrupts to be routed to FIQ rather than IRQ.
These
Using FIQ (if it is available) gives perf a better insight into the
system by allowing code run with interrupts disabled to be profiled.
Signed-off-by: Daniel Thompson
---
arch/arm/include/asm/pmu.h | 4
arch/arm/kernel/perf_event.c | 2 +-
arch/arm/kernel/perf_event_cpu.c | 35
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/13/2015 10:24 AM, Oleg Nesterov wrote:
> Rik,
>
> I can't review this series, I forgot almost everything I learned
> about this code. The only thing I can recall is that it needs
> cleanups and fixes ;) Just a couple of random questions.
>
>
Hi Thomas, Hi Russell:
This RFC is particularly for your attention since it results
directly from feedback I've received from both of you, albeit
quite a few months ago now.
This patchset demonstrates using FIQ to improve the quality of the
PMU trace on ARM systems. To do so it
Hi Rafael / Len,
When i press the power-button on my intel NUC, i get twp ACPI power-events
shortly
after one another (within a second), instead of just one.
It doesn't matter if i have the old /proc/acpi interface enabled or disabled in
the kernel config.
I have tested a few older kernels
On 01/13/2015 11:17 AM, Boris Ostrovsky wrote:
On 01/13/2015 11:07 AM, David Vrabel wrote:
On 13/01/15 15:42, Boris Ostrovsky wrote:
On 01/13/2015 04:52 AM, David Vrabel wrote:
On 13/01/15 08:14, Imre Palik wrote:
From: "Palik, Imre"
In Dom0's the use of the TSC clocksource (whenever it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/13/2015 11:19 AM, Oleg Nesterov wrote:
> On 01/11, r...@redhat.com wrote:
>>
>> @@ -412,8 +412,14 @@ static inline void switch_fpu_prepare(struct
>> task_struct *old, struct task_struc bool preload =
>> tsk_used_math(new) && (use_eager_fpu() ||
Hi Paul,
I started dusting off a series I've been working to implement a relaxed
atomic API in Linux (i.e. things like atomic_read(v, ACQUIRE)) but I'm
having trouble making sense of the ordering semantics we have in mainline
today:
1. Does smp_mb__before_spinlock actually have to order prior
Hi,
On Thu, Dec 18, 2014 at 09:55:10AM +0100, Robert Baldyga wrote:
> Since we can compose gadgets from many functions, there is the problem
> related to gadget breakage while FunctionFS daemon being closed. FFS
> function is userspace code so there is no way to know when it will close
> files
On Mon, 12 Jan 2015 14:43:14 -0700
Jason Gunthorpe wrote:
> On Mon, Jan 12, 2015 at 09:01:34PM +, One Thousand Gnomes wrote:
> > There are plenty of people today who treat the FPGA as an entirely
> > dynamic resource. It's not like flashing a controller, its near
> > immediate.
>
> But this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/12/2015 04:52 PM, Dave Hansen wrote:
> On 01/11/2015 01:46 PM, r...@redhat.com wrote:
>> +/* + * The FPU state used depends on the capabilities of the
>> hardware; the + * registers used for vector instructions on newer
>> hardware are included
Hi Wolfram,
On Tue, Jan 13, 2015 at 03:36:54PM +0100, Wolfram Sang wrote:
> > The driver does not perform DMA, so it's safe to use the relaxed version.
> > From another side, the relaxed io accessor macros are available on all
> > architectures now, so we can use the relaxed versions instead.
>
On Tue, Jan 13, 2015 at 06:20:09PM +0300, Vladimir Davydov wrote:
> On Tue, Jan 13, 2015 at 09:25:44AM -0500, Johannes Weiner wrote:
> > On Tue, Jan 13, 2015 at 12:24:24PM +0300, Vladimir Davydov wrote:
> > > 2. On css offline, empty all list_lru's corresponding to the dying
> > >cgroup by
On Tue, Jan 13, 2015 at 05:09:58PM +0200, Alexander Shishkin wrote:
> Peter Zijlstra writes:
>
> > On Fri, Nov 14, 2014 at 03:43:45PM +0200, Alexander Shishkin wrote:
> >> +static void pt_event_stop(struct perf_event *event, int mode)
> >> +{
> >> + struct pt *pt = this_cpu_ptr(_ctx);
> >> +
>
> + struct ubi_sgl usgl;
Btw, what's in struct ubi_sgl? Can't find that in my tree.
> +static void ubiblock_do_work(struct work_struct *work)
> +{
> + int ret;
> + struct ubiblock_pdu *pdu = container_of(work, struct ubiblock_pdu,
> work);
> + struct request *req =
On Mon, 12 Jan 2015 11:06:08 -0700
Jason Gunthorpe wrote:
> On Sun, Jan 11, 2015 at 10:29:00AM -0600, atull wrote:
> > the FPGA image. If someone wants there to be only one FPGA image on
> > the FGPA forever, they will probably not be using this framework; their
> > FPGA will probably be loaded
On Tue, 13 Jan 2015 23:44:54 +0800
Xunlei Pang wrote:
> rtc_class_ops's set_alarm() shouldn't deal with the alarm date,
> as this is handled in the rtc core.
Please CC the author and ask him. The same applies for the other drivers.
--
Best regards,
Alessandro Zummo,
Tower Technologies -
On Tue, 13 Jan 2015 23:44:50 +0800
Xunlei Pang wrote:
> -EXPORT_SYMBOL(get_seconds);
> +EXPORT_SYMBOL(get_seconds64);
Please leave get_seconds untouched
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
To unsubscribe from this list:
At Tue, 13 Jan 2015 20:15:49 +0530,
Vinod Koul wrote:
>
> On Tue, Jan 13, 2015 at 11:42:07AM +, Qais Yousef wrote:
> > Ping
> >
> > On 12/19/2014 11:38 AM, Qais Yousef wrote:
> > >Fixes the following compilation error:
> > >
> > >include/sound/compress_driver.h: In function
On Tuesday 13 January 2015 23:24:24 Barry Song wrote:
>
> yes, arnd. i also asked Daniel to apply "clocksource: marco: Rename
> marco to atlas7" rebased on this fix here:
> https://git.linaro.org/people/daniel.lezcano/linux.git/commit/81428bbe1d8a073bb3741678ef1d3c1016119c77
Ok
> so this one
On 15/01/13, Richard Guy Briggs wrote:
> On 15/01/08, Calvin Owens wrote:
> > This reverts 543bc6a1a987 "AUDIT: Allow login in non-init namespaces".
> >
> > This commit incorrectly assumes that libpam treats -ECONNREFUSED as
> > an indicator that audit is disabled, and -EPERM or any other error
>
On Tue, Jan 13, 2015 at 11:44:44PM +0800, Ming Lei wrote:
> Follows benefits from using kernel aio in loop:
> - avoid double cache, and memory usage decreased a lot
> - system load gets much decreased
This seems to conflate two changes:
1) use direct I/O
2) use aio (require 1)
On Tue, 13 Jan 2015 23:44:51 +0800
Xunlei Pang wrote:
> This patch resolves them by:
> - Repalce get_seconds() with get_seconds64()
> - Replace rtc_time_to_tm() with rtc_time64_to_tm()
> - Change test_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
so we no more have a non time64 test
On 01/11, r...@redhat.com wrote:
>
> @@ -412,8 +412,14 @@ static inline void switch_fpu_prepare(struct task_struct
> *old, struct task_struc
> bool preload = tsk_used_math(new) && (use_eager_fpu() ||
>new->thread.fpu_counter > 5);
> if
On Tue, 13 Jan 2015 23:44:52 +0800
Xunlei Pang wrote:
> From: Xunlei Pang
>
> This driver has a number of y2038/y2106 issues.
This should probably be evaluated by
Linus Walleij
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
To
On Tue, Dec 3, 2013 at 10:00 PM, Sachin Kamat wrote:
> Hi Abhilash,
>
> On 3 December 2013 20:16, Abhilash Kesavan wrote:
>> Hi Yadwinder and Sachin,
>
>> CC'ing Doug and Andrew who have also worked on ASV.
>>
>> I tested these patches on a 5250 Chromebook after modifying the
>> cpufreq code and
On Tue, Jan 13, 2015 at 03:16:10PM +, Qais Yousef wrote:
> On 01/13/2015 02:59 PM, Vinod Koul wrote:
> >>being NULL, hence when trying to set rtd a few lines below we get an oops.
> >It is a good practice to add the oops here
> Will this really be helpful? I think it'll be more clutter (the
On Tue, Jan 13, 2015 at 04:02:20PM +0530, Kiran Raparthy wrote:
> Hi Felipe,
>
> On 1 December 2014 at 11:09, Kiran Raparthy wrote:
> > Hi Felipe,
> >
> > On 25 November 2014 at 20:15, Felipe Balbi wrote:
> >> On Tue, Nov 25, 2014 at 07:06:18AM +, Peter Chen wrote:
> >>>
> >>> >
> >>> >
2015-01-13 00:27+, Wu, Feng:
> > On 09/01/2015 15:54, Radim Krčmář wrote:
> > > There are two points relevant to this patch in new KVM's implementation,
> > > ("KVM: x86: amend APIC lowest priority arbitration",
> > > https://lkml.org/lkml/2015/1/9/362)
> > >
> > > 1) lowest priority depends
We've been getting this warning for ages:
./usr/include/linux/kexec.h:61: userspace cannot reference function or variable
defined in the kernel
There is no proper fix for this file, as the declaration is meant for
user space, not for the kernel, so we should work around it the
same way that we
On 01/13/2015 08:40 AM, Bart Tanghe wrote:
On 01/10/2015 05:38 PM, Stephen Warren wrote:
On 01/05/2015 08:33 AM, Bart Tanghe wrote:
To probe the bcm2835-pwm driver properly, this dts bindings has to be added
to the bcm2835 dtsi file.
In expectation of a bcm2835 clock driver, I've added
On Tue, 13 Jan 2015 23:44:49 +0800
Xunlei Pang wrote:
> + else if (rtc->ops->set_mmss64) {
> + ;
> +
> + secs64 = rtc_tm_to_time64(tm);
time64_t secs64 = rtc_tm_to_time64(tm);
would do as well. add spaces, variables
and empty lines only when required for
On 01/13/2015 11:07 AM, David Vrabel wrote:
On 13/01/15 15:42, Boris Ostrovsky wrote:
On 01/13/2015 04:52 AM, David Vrabel wrote:
On 13/01/15 08:14, Imre Palik wrote:
From: "Palik, Imre"
In Dom0's the use of the TSC clocksource (whenever it is stable
enough to
be used) instead of the Xen
On Tue, Jan 13, 2015 at 11:05:22AM +0100, Linus Walleij wrote:
> >> I am worried that there is something in your reasoning that sort of
> >> assumes all pin controllers mux pins one-by-one and not in groups.
> >> How do we make it impossible to write a device tree that also
> >> make hardware that
var->yoffset is of the type __u32, hence the comparison will always
be false.
Signed-off-by: Sudip Mukherjee
---
drivers/video/fbdev/hgafb.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/hgafb.c b/drivers/video/fbdev/hgafb.c
index 5ff9fe2..15d3ccf
This patch utilizes the previously introduced checker to check
register usage for probed ARM instruction and saves it in a mask.
A further patch will use such information to avoid simulation or
emulation.
Signed-off-by: Wang Nan
Reviewed-by: Jon Medhurst
Signed-off-by: Jon Medhurst
---
This
2015-01-13 16:45 GMT+02:00 Paul Clements :
> All,
>
> I've maintained the NBD driver since 2003, but alas, I no longer have
> the time and energy to continue maintaining it. If someone would like
> to take over, let me know.
Hi Paul,
could you please describe
- how wide is NBD usage today (any
Not all architectures are able to call __builtin_return_address().
On ARM, the mISDN code produces this warning:
hardware/mISDN/w6692.c: In function 'w6692_dctrl':
hardware/mISDN/w6692.c:1181:75: warning: unsupported argument to
'__builtin_return_address'
pr_debug("%s: %s dev(%d) open from
On 13/01/15 15:42, Boris Ostrovsky wrote:
> On 01/13/2015 04:52 AM, David Vrabel wrote:
>> On 13/01/15 08:14, Imre Palik wrote:
>>> From: "Palik, Imre"
>>>
>>> In Dom0's the use of the TSC clocksource (whenever it is stable
>>> enough to
>>> be used) instead of the Xen clocksource should not
On Tue, Jan 13, 2015 at 04:37:27PM +0530, Vinayak Menon wrote:
> @@ -1392,6 +1392,44 @@ int isolate_lru_page(struct page *page)
> return ret;
> }
>
> +static int __too_many_isolated(struct zone *zone, int file,
> + struct scan_control *sc, int safe)
> +{
> + unsigned long
From: Namjae Jeon
Add finsert command for fallocate FALLOC_FL_INSERT_RANGE flag.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
Reviewed-by: Brian Foster
---
io/prealloc.c | 39 ++-
1 file changed, 38 insertions(+), 1 deletion(-)
diff --git
Under pressure, the imx.c device driver may transfer the same data multiple
times.
Reason:
Function imx_dma_tx checks for an active DMA transfer by calling
dmaengine_tx_status. The return value may indicate that no transfer is
running while the dma_tx_callback function is still being executed.
From: Namjae Jeon
This testcase(042) tries to test various corner cases with delayed extents and
pre-existing holes for finsert range functionality over different type of
extents.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
tests/generic/042 | 65
From: Namjae Jeon
This testcase(040) tries to test various corner cases with delayed extents
for finsert range functionality over different type of extents.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
tests/generic/040 | 65 +
From: Namjae Jeon
This commit adds insert operation support for fsstress, which is
meant to exercise fallocate FALLOC_FL_INSERT_RANGE support.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
Reviewed-by: Brian Foster
---
ltp/fsstress.c | 19 ---
src/global.h |
From: Namjae Jeon
This testcase(041) tries to test various corner cases with pre-existing holes
for finsert range functionality over different type of extents.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
tests/generic/041 | 65
From: Namjae Jeon
This testcase(039) tries to test various corner cases for finsert range
functionality over different type of extents.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
---
common/punch |5
common/rc |2 +-
tests/generic/039 |
From: Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for Ext4.
1) Make sure that both offset and len are block size aligned.
2) Update the i_size of inode by len bytes.
3) Compute the file's logical block number against offset. If the computed
block number is not the
From: Namjae Jeon
This commit adds fallocate FALLOC_FL_INSERT_RANGE support for fsx.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
Cc: Brian Foster
---
Changelog
v8:
- create TRIM_OFF() and TRIM_LEN() and redeine redefine TRIM_OFF_LEN().
ltp/fsx.c | 122
From: Namjae Jeon
FALLOC_FL_INSERT_RANGE command is the opposite command of
FALLOC_FL_COLLAPSE_RANGE that is needed for advertisers or someone who want to
add some data in the middle of file. FALLOC_FL_INSERT_RANGE will create space
for writing new data within a file after shifting extents to
From: Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS.
1) Make sure that both offset and len are block size aligned.
2) Update the i_size of inode by len bytes.
3) Compute the file's logical block number against offset. If the computed
block number is not the
From: Namjae Jeon
This testcase(043) tries to test finsert range a single alternate block
mulitiple times and test merge code of collase range.
Signed-off-by: Namjae Jeon
Signed-off-by: Ashish Sangwan
Cc: Brian Foster
---
Changelog
v8:
- use MKFS_OPTION to use blocksize in configuration and
From: Namjae Jeon
In continuation of the work of making the process of non linear editing of
media files faster, we introduce here the new flag FALLOC_FL_INSERT_RANGE
for fallocate.
This flag will work opposite to the FALLOC_FL_COLLAPSE_RANGE flag.
As such, specifying FALLOC_FL_INSERT_RANGE
On Tue, Jan 13, 2015 at 10:55:26AM -0500, Chris Metcalf wrote:
> On 1/13/2015 4:45 AM, Michael S. Tsirkin wrote:
> >On Mon, Jan 12, 2015 at 07:08:36PM -0500, Chris Metcalf wrote:
> >>The key changes are to copy the x86 definition of __inttype(), and then to
> >>arrange to use an intermediate
>>> On 13.01.15 at 14:29, wrote:
> Em Tue, Jan 13, 2015 at 08:48:35AM +, Jan Beulich escreveu:
>> Arnaldo,
>>
>> considering that tools/include/ gets used by other than just perf, in
>> particular arch/x86/vdso/vdso2c.c, would you mind clarifying how
>> "tools: Move bitops.h from
[...]
>> +EXPORT_SYMBOL(ssp_common_setup_buffer);
>> diff --git a/drivers/iio/common/ssp_sensors/ssp_iio_sensor.h
>> b/drivers/iio/common/ssp_sensors/ssp_iio_sensor.h
>> new file mode 100644
>> index 000..4b79be0
>> --- /dev/null
>> +++ b/drivers/iio/common/ssp_sensors/ssp_iio_sensor.h
>> @@
On 01/13/15 at 03:06pm, David Laight wrote:
> OK, ht->mutes saves the day.
> Might be worth a comment to save people looking at the code in isolation
> from worrying and doing a bit search.
> OTOH it might be obvious from a slightly larger fragment than the diff.
Good idea. Will do this. Also,
On Tue, Jan 13, 2015 at 04:54:11PM +0100, Jean-Francois Moine wrote:
> 4 streams on 4 different APs (sources) should work, but 4 streams from
> a same source should be detailed.
I'd like to know how you intend to wire up four different I2S sources
to the TDA998x.
Remember, an I2S source produces
On Tue, 2015-01-13 at 12:57 +0100, Bilel DRIRA wrote:
> ERROR: else should follow close brace '}'
[]
> diff --git a/drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c
> b/drivers/staging/ft1000/ft1000-pcmcia/ft1000_hw.c
[]
> @@ -572,8 +572,7 @@ static void ft1000_hbchk(u_long data)
>
* Tomi Valkeinen [150113 02:14]:
> On 03/12/14 23:33, Marek Belisko wrote:
> > Add handling for gta04 tv out chain:
> > venc -> opa362 -> svideo
> >
> > Use invert-polarity in venc node because opa362
> > is doing polarity inversion also.
> >
> > Signed-off-by: Marek Belisko
> > ---
> >
On Mon, Jan 12, 2015 at 2:31 AM, Ulf Hansson wrote:
> On 5 January 2015 at 20:52, Bjorn Andersson wrote:
>> On Sun, Dec 21, 2014 at 7:01 PM, Tim Kryger wrote:
>>> On Wed, Dec 17, 2014 at 11:57 AM, Bjorn Andersson wrote:
>> [..]
Non-the-less, feel free to propose a patch and I will give it
On Tue, 13 Jan 2015 12:27:15 +
Russell King - ARM Linux wrote:
> On Tue, Jan 13, 2015 at 01:21:58PM +0100, Philipp Zabel wrote:
> > I wonder if it wouldn't be nicer to have the AP# and type in the device
> > tree and then calculate the register value from that in the driver.
> >
> >
On Thu, Jan 08, 2015 at 11:15:03PM -0500, Johannes Weiner wrote:
> It was convenient to have the generic function handle it, as all
> callsites agreed. Subsequent patches will add new user interfaces
> that do not want to support the "-1" special string.
>
> Signed-off-by: Johannes Weiner
(2015/01/07 16:34), Wang Nan wrote:
> This patch series shows early kprobe, a mechanism allows users to track
> events at very early. It should be useful for optimization of system
> booting. This can also be used by BSP developers to hook their platform
> specific procedures at kernel booting
On Wed, Dec 31, 2014 at 11:23:50AM +0100, Wolfram Sang wrote:
> On Mon, Dec 22, 2014 at 09:08:22PM +0530, Vinod Koul wrote:
> > On Sun, Dec 21, 2014 at 10:14:27PM +0100, Wolfram Sang wrote:
> > > This platform_driver does not need to set an owner, it will be populated
> > > by the
> > > driver
* Roger Quadros [150113 04:26]:
> The sata_ref_clk is a reference clock to the SATA phy.
> This fixes SATA malfunction across suspend/resume or when
> SATA driver is used as a module.
>
> Signed-off-by: Roger Quadros
Acked-by: Tony Lindgren
> ---
> arch/arm/boot/dts/omap5.dtsi | 4 ++--
> 1
On Mon, Jan 5, 2015 at 11:52 AM, Bjorn Andersson wrote:
> On Sun, Dec 21, 2014 at 7:01 PM, Tim Kryger wrote:
>> On Wed, Dec 17, 2014 at 11:57 AM, Bjorn Andersson wrote:
> [..]
>>> Non-the-less, feel free to propose a patch and I will give it a test.
>>
>> Lets start with the simplest change
* Roger Quadros [150113 04:26]:
> The sata_ref_clk is a reference clock to the SATA phy.
> This fixes SATA malfunction across suspend/resume or when
> SATA driver is used as a module.
>
> Signed-off-by: Roger Quadros
Acked-by: Tony Lindgren
> ---
> arch/arm/boot/dts/dra7.dtsi | 4 ++--
> 1
Le 13/01/2015 02:24, Bo Shen a écrit :
> Hi Alexandre,
>
> On 01/13/2015 02:42 AM, Alexandre Belloni wrote:
>> at91rm9200_dt_initialize() is doing the same as at91_dit_initialize(), use
>> that
>
> s/at91_dit_initialize/at91_dt_initialize
Alex I'll correct that when including it to the
* Roger Quadros [150113 04:26]:
> Hi,
>
> During system suspend L3INIT_960M_GFCLK and L3INIT_480M_GFCLK clocks remain
> active on the DRA7 platform. This is because the pipe3 driver doesn't shut
> them off as part of .suspend(). Patch 1 addresses this issue.
>
> SATA on both OMAP5 and DRA7
On 1/13/2015 4:45 AM, Michael S. Tsirkin wrote:
On Mon, Jan 12, 2015 at 07:08:36PM -0500, Chris Metcalf wrote:
The key changes are to copy the x86 definition of __inttype(), and then to
arrange to use an intermediate integral type that gets assigned to or from
the actual typed value so as to
On 01/11, r...@redhat.com wrote:
>
> @@ -382,6 +382,7 @@ static inline void drop_init_fpu(struct task_struct *tsk)
> else
> fxrstor_checking(_xstate_buf->i387);
> }
> + clear_thread_flag(TIF_LOAD_FPU);
OK, in this case tsk should be current. Still I
On Tue, Jan 13, 2015 at 06:46:36AM +, Pratyush Anand wrote:
> On Monday 12 January 2015 11:00 PM, Will Deacon wrote:
> > On Fri, Jan 09, 2015 at 05:13:29PM +, Pratyush Anand wrote:
> >> On Friday 09 January 2015 09:16 PM, Will Deacon wrote:
> >>> On Thu, Jan 08, 2015 at 05:28:37PM +,
We hit use after free on dereferncing pointer to task_smack struct in
smk_of_task() called from smack_task_to_inode().
task_security() macro uses task_cred_xxx() to get pointer to the task_smack.
task_cred_xxx() could be used only for non-pointer members of task's
credentials. It cannot be used
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Change mc13xxx_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver should not have any remaining
y2038/y2106 issues.
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_tm_to_time() with rtc_tm_to_time64()
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Change ab3100_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver
From: Xunlei Pang
We want to convert mxc_rtc_set_mmss() to use rtc_class_ops's set_mmss64(),
but it uses get_alarm_or_time()/set_alarm_or_time() internal interfaces
which are y2038 unsafe.
So here as a separate patch, it converts these two internal interfaces
of "mxc" to use safe time64_t to
On Mon, Dec 29, 2014 at 03:48:48PM +0200, Mika Westerberg wrote:
> ACPI specification allows I2C devices with multiple addresses. The current
> implementation goes over all addresses and assigns the last one to the
> device. This is typically not the primary address of the device.
>
> Instead of
On Mon, Jan 12, 2015 at 03:37:16PM -0800, Andrew Morton wrote:
> On Thu, 8 Jan 2015 23:15:04 -0500 Johannes Weiner wrote:
>
> > Introduce the basic control files to account, partition, and limit
> > memory using cgroups in default hierarchy mode.
> >
> > This interface versioning allows us to
From: Xunlei Pang
Currently the rtc_class_op's set_mmss() function takes a 32bit second
value (on 32bit systems), which is problematic for dates past y2038.
This patch provides a safe version named set_mmss64() using y2038 safe
time64_t.
After this patch, set_mmss() is deprecated and all its
On Mon, Dec 29, 2014 at 02:01:30PM +0100, Krzysztof Kozlowski wrote:
> While splitting device control in db08425ebd51 ("dmaengine: k3:
> Split device_control") new function with the same 'k3_dma_resume' name
> was added, leading to build error:
>
> drivers/dma/k3dma.c:823:12: error: conflicting
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Replace rtc_tm_to_time() with rtc_tm_to_time64()
- Change mxc_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, the driver
From: Xunlei Pang
This patch series relies on a former patchset[1], it provides y2038/y2106
safe rtc_class_ops.set_mmss64(), and converts some possible users of set_mmss()
to use set_mmss64(), in the hope that making these users(i.e. rtc drivers)
y2038/y2106 safe.
The first version of this
From: Xunlei Pang
Change alpha_rtc_set_mmss() and remote_set_mmss() to use
rtc_class_ops's set_mmss64().
Signed-off-by: Xunlei Pang
---
arch/alpha/kernel/rtc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/alpha/kernel/rtc.c b/arch/alpha/kernel/rtc.c
index
From: Xunlei Pang
As part of addressing "y2038 problem" for in-kernel uses, this
patch adds safe get_seconds64() using time64_t.
After this patch, get_seconds() is deprecated and all its call sites
will be fixed using get_seconds64(), after that it can be removed.
Signed-off-by: Xunlei Pang
From: Xunlei Pang
This driver has a number of y2038/y2106 issues.
This patch resolves them by:
- Repalce get_seconds() with get_seconds64()
- Replace rtc_time_to_tm() with rtc_time64_to_tm()
- Change test_rtc_set_mmss() to use rtc_class_ops's set_mmss64()
After this patch, this driver should
From: Xunlei Pang
rtc_class_ops's set_alarm() shouldn't deal with the alarm date,
as this is handled in the rtc core.
See rtc_dev_ioctl()'s RTC_ALM_SET and RTC_WKALM_SET cases.
Signed-off-by: Xunlei Pang
---
drivers/rtc/rtc-mxc.c | 22 --
1 file changed, 4 insertions(+),
On 01/10/2015 05:38 PM, Stephen Warren wrote:
> On 01/05/2015 08:33 AM, Bart Tanghe wrote:
>> To probe the bcm2835-pwm driver properly, this dts bindings has to be added
>> to the bcm2835 dtsi file.
>> In expectation of a bcm2835 clock driver, I've added fixed-clock clock
>> binding.
>> To
From: Dave Kleikamp
This adds an interface that lets kernel callers submit aio iocbs without
going through the user space syscalls. This lets kernel callers avoid
the management limits and overhead of the context. It will also let us
integrate aio operations with other kernel apis that the
Part of the patch is based on Dave's previous post.
This patch submits I/O to fs via kernel aio, and we
can obtain following benefits:
- double cache in both loop file system and backend file
gets avoided
- context switch decreased a lot, and finally CPU utilization
So that users can control if kernel aio is used to submit I/O.
Signed-off-by: Ming Lei
---
drivers/block/loop.c | 33 +
drivers/block/loop.h |1 +
2 files changed, 34 insertions(+)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index
For pages from kernel AIO, it is required to dirty
them before direct IO.
The idea is borrowd from Dave previous post.
Also set ->should_dirty only for ITER_IOVEC pages
based on recent discussion in following link:
http://marc.info/?t=14190455683=1=2
Cc: Maxim Patlasov
Cc: Omar
Hi Guys,
The 1st two patches introduce kernel AIO support, most of
is borrowed from previous Dave's work, and thanks to ITER_BVEC,
it is much simper to implement kernel AIO now.
The last two patches applies kernel aio to loop-mq.
Follows benefits from using kernel aio in loop:
- avoid
Hi,
On Tue, Jan 13, 2015 at 06:51:40AM +, Peter Chen wrote:
>
> > See below error message:
> > CC [M] drivers/gpu/drm/nouveau/core/subdev/vm/nv50.o
> > CC [M] drivers/staging/lustre/lnet/selftest/module.o
> > drivers/usb/gadget/function/f_uac1.c: In function ‘f_audio_free_inst’:
> >
On 01/13/2015 04:52 AM, David Vrabel wrote:
On 13/01/15 08:14, Imre Palik wrote:
From: "Palik, Imre"
In Dom0's the use of the TSC clocksource (whenever it is stable enough to
be used) instead of the Xen clocksource should not cause any issues, as
Dom0 VMs never live-migrated. The TSC
On 01/13/2015 04:24 PM, Arnd Bergmann wrote:
On Tuesday 13 January 2015 15:27:05 Daniel Lezcano wrote:
On 01/13/2015 03:22 PM, Arnd Bergmann wrote:
A recent rework of the driver left an obviously unused variable
around, and now the compiler complains:
clocksource/timer-marco.c: In function
601 - 700 of 2050 matches
Mail list logo
