Use the 24-bit Time-Of-Day clock in CIA B, which is clocked by HSYNC.
Signed-off-by: Geert Uytterhoeven
---
1. Completely untested! It does compile ;-)
2. Is a 24-bit counter running at 15-31 kHz good enough?
Two cascaded 16-bit CIA timers running from the 700 kHz E-clock would
be
On Mon 09-09-13 09:45:52, Olof Johansson wrote:
> On Mon, Sep 9, 2013 at 7:39 AM, Jan Kara wrote:
> > On Sun 08-09-13 20:21:54, Olof Johansson wrote:
> >> On Fri, Sep 06, 2013 at 10:52:52AM +0200, Geert Uytterhoeven wrote:
> >> > On Fri, Sep 6, 2013 at 9:19 AM, Stephen Rothwell
> >> > wrote:
>
On 08/26/2013 12:36 AM, Keerthy wrote:
> The Patch adds nodes for TPS659038 PMIC for DRA7 boards.
>
> It is based on top of:
> http://comments.gmane.org/gmane.linux.ports.arm.omap/102459.
>
> Documentation:Documentation/devicetree/bindings/mfd/palmas.txt
>
On Sep 9, 2013, at 12:48 PM, Rohit Vaswani wrote:
> On 9/6/2013 2:50 PM, Olof Johansson wrote:
>> Hi,
>>
>> Some comments below.
>>
>> On Fri, Sep 06, 2013 at 12:32:22PM -0700, Rohit Vaswani wrote:
>>> This patch adds basic board support for APQ8074 Dragonboard
>>>
>>> dtb-$(CONFIG_ARCH_MSM)
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Imre Deak
commit 77fa4cbd5fa389e28419bbe8ac491b5fdd54840d upstream.
Fix the typo introduced in
commit 1a2eb4604b85c5efb343da8a4dcf41288fcfca85
Author: Keith Packard
Date: Wed Nov 16
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicolas Dichtel
commit 85dfb745ee40232876663ae206cba35f24ab2a40 upstream.
This field was left uninitialized. Some user daemons perform check against this
field.
Signed-off-by: Nicolas
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit fb615499f0ad28ed74201c1cdfddf9e64e205424 upstream.
The recent commit to delay the release of kobject triggered NULL
dereferences of opti9xx drivers. The cause is
On Mon, 9 Sep 2013 10:56:56 -0700
"Paul E. McKenney" wrote:
> Although I do like rcu_is_active() better than rcu_read_check(), my
> concern with rcu_is_active() is that it can easily be mistaken for a
> global state rather than a per-CPU/thread/task/whatever state.
rcu_is_active_local();
On Mon, Sep 9, 2013 at 7:22 PM, Greg Kroah-Hartman
wrote:
> On Mon, Sep 09, 2013 at 10:08:19AM -0700, Guenter Roeck wrote:
>> On Mon, Sep 09, 2013 at 09:39:02AM -0700, Greg Kroah-Hartman wrote:
>> > On Mon, Sep 09, 2013 at 06:40:12AM -0700, Christoph Hellwig wrote:
>> > > On Sun, Sep 08, 2013 at
On Mon, Sep 09, 2013 at 02:01:15PM -0400, Steven Rostedt wrote:
> On Wed, Jul 24, 2013 at 03:02:45PM +0100, Ben Hutchings wrote:
> > 3.2.49-rc1 review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Hauke Mehrtens
> >
> > commit
On Mon, Sep 09, 2013 at 02:46:57PM -0400, Waiman Long wrote:
> I am fine with your proposed change as long as it gets the job done.
I suspect that the real problem is the unlock part of read_seqretry_or_unlock();
for d_walk() we want to be able to check if we need retry and continue walking
if
Op 9 sep. 2013, om 20:27 heeft Joel Fernandes het volgende
geschreven:
> On 09/09/2013 10:51 AM, Koen Kooi wrote:
>>
>> Op 9 sep. 2013, om 17:23 heeft Kevin Hilman het
>> volgende geschreven:
>>
>>> Koen Kooi writes:
>>>
The BeagleBone Black is basically a regular BeagleBone with
On Mon, Sep 09, 2013 at 07:21:11PM +0100, Al Viro wrote:
> Actually, it's better for prepend_path() as well, because it's actually
>
> rcu_read_lock();
> seq = read_seqbegin(_lock);
> again:
>
> if (error)
> goto done;
>
> if
Hi Grant,
On 04/08/13 05:35 AM, Haojian Zhuang wrote:
On Sat, Aug 3, 2013 at 5:24 AM, Graeme Smecher
wrote:
The pca957x driver supports a handful of I2C GPIO expanders from NXP, Maxim,
and TI. For the PCA9574 and PCA9575 devices only, the driver resets the GPIO
level and direction in the
On Mon, 2013-09-09 at 09:27 -0700, H. Peter Anvin wrote:
> On 09/09/2013 08:49 AM, Matthew Garrett wrote:
> > +1: Secure mode. If set, userspace will be unable to perform direct access
> > +to PCI devices, port IO access, access system memory directly via
> > +/dev/mem and /dev/kmem,
On 09/09/2013 10:51 AM, Koen Kooi wrote:
>
> Op 9 sep. 2013, om 17:23 heeft Kevin Hilman het volgende
> geschreven:
>
>> Koen Kooi writes:
>>
>>> The BeagleBone Black is basically a regular BeagleBone with eMMC and HDMI
>>> added,
>>> so create a common dtsi both can use.
>>>
>>> IMPORTANT:
On Mon, 2013-09-09 at 11:40 -0700, David Lang wrote:
> On Mon, 9 Sep 2013, Matthew Garrett wrote:
>
> > On Mon, 2013-09-09 at 11:25 -0700, David Lang wrote:
> >
> >> Given that we know that people want signed binaries without blocking
> >> kexec, you
> >> should have '1' just enforce module
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Russ Anderson
commit 21ea9f5ace3a7317cc3ba1fbc749758021a83136 upstream.
"cat /sys/devices/system/memory/memory*/removable" crashed the system.
The problem is that show_mem_removable()
On Mon, Sep 09, 2013 at 07:36:08PM +0100, Al Viro wrote:
> FWIW, what I propose is this (just the d_path-related parts):
Grrr... It's still the wrong set of primitives ;-/ Nevermind that one...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
__fscache_check_consistency() does not decrement the count of operations
active after it finishes in the success case. This leads to a hung tasks on
cookie de-registration (commonly in inode eviction).
INFO: task kworker/1:2:4214 blocked for more than 120 seconds.
kworker/1:2 D
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tejun Heo
commit b22ce2785d97423846206cceec4efee0c4afd980 upstream.
If !PREEMPT, a kworker running work items back to back can hog CPU.
This becomes dangerous when a self-requeueing
On Mon, 2013-09-09 at 15:01 -0400, valdis.kletni...@vt.edu wrote:
> On Mon, 09 Sep 2013 11:25:38 -0700, David Lang said:
>
> > Given that we know that people want signed binaries without blocking kexec,
> > you
> > should have '1' just enforce module signing and '2' (or higher) implement a
> >
On Mon, 9 Sep 2013 19:39:04 +0100
Ben Hutchings wrote:
> On Mon, Sep 09, 2013 at 02:01:15PM -0400, Steven Rostedt wrote:
> > On Wed, Jul 24, 2013 at 03:02:45PM +0100, Ben Hutchings wrote:
> > > 3.2.49-rc1 review patch. If anyone has any objections, please let me
> > > know.
> > >
> > >
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Russell King
commit e39e3f3ebfef03450cf7bfa7a974a8c61f7980c8 upstream.
FIQ should no longer copy the FIQ code into the user visible vector
page. Instead, it should use the hidden page.
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit 2a3ba63c235fdcd37f6451bdf4a0c7865a3930cf upstream.
IBSS needs to release the channel context when leaving
but I evidently missed that. Fix it.
Signed-off-by:
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kevin Hilman
commit 3f0fa9a808f98fa10a18ba2a73f13d65fda990fb upstream.
The use of WARN_ON() needs the definitions from bug.h, without it
you can get:
include/linux/regmap.h: In
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helmut Schaa
commit d2e9fc141e2aa21f4b35ee27072d84e9aa6e2ba0 upstream.
ath9k_htc adds padding between the 802.11 header and the payload during
TX by moving the header. When handing the
This is the start of the review cycle for the Linux 3.8.13.9 stable kernel.
This version contains 24 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
On Mon, 09 Sep 2013 11:25:38 -0700, David Lang said:
> Given that we know that people want signed binaries without blocking kexec,
> you
> should have '1' just enforce module signing and '2' (or higher) implement a
> full
> lockdown including kexec.
> Or, eliminate the -1 permanently insecure
On 09/09/2013 01:43 PM, Koen Kooi wrote:
>
> Op 9 sep. 2013, om 20:27 heeft Joel Fernandes het volgende
> geschreven:
>
>> On 09/09/2013 10:51 AM, Koen Kooi wrote:
>>>
>>> Op 9 sep. 2013, om 17:23 heeft Kevin Hilman het
>>> volgende geschreven:
>>>
Koen Kooi writes:
> The
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Al Viro
commit b177a29251081576df35cfbcb0f7d7c80deceb8b upstream.
Signed-off-by: Al Viro
[ kamal: 3.8.y-stable prereq for:
"f5f6cbb powerpc: Don't Oops when accessing
Em Sat, Sep 07, 2013 at 08:20:10AM -0600, David Ahern escreveu:
> On 9/6/13 1:40 PM, Adrian Hunter wrote:
> >Ensure the id_pos is correct when perf_evlist__open()
> >is used.
>
> The commit log should reference 7556257 and breakage of 'kvm stat
> live'; helps identify patches when backporting.
>
On Mon, 2013-09-09 at 11:53 -0700, David Lang wrote:
> So is there a way to unify these different things rather than creating yet
> another different knob?
We haven't found one that people consider generally acceptable.
--
Matthew Garrett
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Trond Myklebust
commit 347e2233b7667e336d9f671f1a52dfa3f0416e2c upstream.
Some architectures, such as ARM-32 do not return the same base address
when you call kmap_atomic() twice on the
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Russell King
commit 2ba85e7af4c639d933c9a87a6d7363f2983d5ada upstream.
Aaro Koskinen reports the following oops:
Installing fiq handler from c001b110, length 0x164
Unable to handle
On Mon, 9 Sep 2013, Matthew Garrett wrote:
On Mon, 2013-09-09 at 11:40 -0700, David Lang wrote:
On Mon, 9 Sep 2013, Matthew Garrett wrote:
On Mon, 2013-09-09 at 11:25 -0700, David Lang wrote:
Given that we know that people want signed binaries without blocking kexec, you
should have '1'
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chen Gang
commit 5676005acf26ab7e924a8438ea4746e47d405762 upstream.
need set '\0' for 'local_buffer'.
SPLPAR_MAXLENGTH is 1026, RTAS_DATA_BUF_SIZE is 4096. so the contents of
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 2ca320e294a738c9134a71b5029de05edbfc7aad upstream.
Without the dynamic minor assignment, HDMI codec may have less PCM
instances than the number of pins, which
On Mon, 2013-09-09 at 11:25 -0700, David Lang wrote:
> Given that we know that people want signed binaries without blocking kexec,
> you
> should have '1' just enforce module signing and '2' (or higher) implement a
> full
> lockdown including kexec.
There's already a kernel option for that.
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jakob Bornecrantz
commit 6e4dcff3adbf25acb87e74500a58e3c07bdec40f upstream.
This fixes the piglit test texturing/max-texture-size
causing the VM to die due to a too large SVGA command.
On Mon, 9 Sep 2013, valdis.kletni...@vt.edu wrote:
On Mon, 09 Sep 2013 11:49:34 -0400, Matthew Garrett said:
So, this is my final attempt at providing the functionality I'm interested
in without inherently tying it to Secure Boot. There's strong parallels
between the functionality that I'm
On Mon, 2013-09-09 at 08:20 +, Morales, Alejandra wrote:
> mounted and there is no application using them at the moment, so that
> I was expecting that none
> of them receive file system requests. Indeed the SATA HD does not
> receive any requests unless I
> mount or unmount it, but the USB HD
Hi,
On Mon, Sep 09, 2013 at 04:26:38PM +0200, Koen Kooi wrote:
>
> Op 9 sep. 2013, om 16:15 heeft Felipe Balbi het volgende
> geschreven:
>
> > Hi,
> >
> > On Mon, Sep 09, 2013 at 03:45:50PM +0200, Koen Kooi wrote:
> >> The BeagleBone Black is basically a regular BeagleBone with eMMC and
Signed-off-by: Albert Pool
Reported-by: Michael Landrum
---
drivers/net/wireless/ath/ar5523/ar5523.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ar5523/ar5523.c
b/drivers/net/wireless/ath/ar5523/ar5523.c
index 17d7fec..280fc3d 100644
---
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paul Mackerras
commit bdbc29c19b2633b1d9c52638fb732bcde7a2031a upstream.
On 64-bit, __pa(_var) gets miscompiled by recent versions of
gcc as something like:
addis
David,
Can I get a sign off on this?
Thanks,
- Milosz
On Mon, Sep 9, 2013 at 2:28 PM, Milosz Tanski wrote:
> __fscache_check_consistency() does not decrement the count of operations
> active after it finishes in the success case. This leads to a hung tasks on
> cookie de-registration (commonly
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrey Vagin
commit 6f6b8951897e487ea6f77b90ea01f70a9c363770 upstream.
If the system had a few memory groups and all of them were destroyed,
memcg_limited_groups_array_size has non-zero
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sujith Manoharan
commit 19c361608ce3e73f352e323262f7e0a8264be3af upstream.
The PLL hang workaround is required only for AR9330 and
AR9340. This issue was first observed on an AP121 and
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eugene Surovegin
commit d220980b701d838560a70de691b53be007e99e78 upstream.
This solves a problem observed in kexec'ed kernel where 200ms timeout is
too short and bootconsole fails to
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stanislaw Gruszka
commit b2fcc0aee58a3435566dd6d8501a0b32f28b upstream.
My current 3.11 fix:
commit 788f7a56fce1bcb2067b62b851a086fca48a0056
Author: Stanislaw Gruszka
Date: Thu
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit d3d3835ce919438c00c5d1270d6f9d6ffea59d03 upstream.
Yet another entry, just use the existing fixup for this machine, too.
Reported-by: "Nathanael D. Noblet"
On 09/09/2013 02:36 PM, Al Viro wrote:
On Mon, Sep 09, 2013 at 07:21:11PM +0100, Al Viro wrote:
Actually, it's better for prepend_path() as well, because it's actually
rcu_read_lock();
seq = read_seqbegin(_lock);
again:
if (error)
goto done;
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andy Lutomirski
commit d661684cf6820331feae71146c35da83d794467e upstream.
This is a security bug.
The follow-up will fix nsproxy to discourage this type of issue from
happening again.
On Mon, Sep 09, 2013 at 02:36:39PM -0400, Steven Rostedt wrote:
> On Mon, 9 Sep 2013 10:56:56 -0700
> "Paul E. McKenney" wrote:
>
>
> > Although I do like rcu_is_active() better than rcu_read_check(), my
> > concern with rcu_is_active() is that it can easily be mistaken for a
> > global state
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Pali=20Roh=C3=A1r?=
commit 0ff42c5af6031c776d6079d67cd2615121e62fb8 upstream.
In commit 77145f1cbdf8d28b46ff8070ca749bad821e0774 was introduced
error which cause that
3.8.13.9 -stable review patch. If anyone has any objections, please let me
know.
--
From: Benjamin Herrenschmidt
commit f5f6cbb61610b7bf9d9d96db9c3979d62a424bab upstream.
/proc/powerpc/lparcfg is an ancient facility (though still actively used)
which allows access to some
The "id" variable was being incremented in common code, but only
initialized and used in IPv4 code. We move the increment to the IPv4
code too, and then legitimately use the uninitialized_var() macro to
avoid the gcc 4.6 warning that 'id' may be used uninitialized.
Note that gcc 4.7 does not
Il 09/09/2013 01:40, Dave Chinner ha scritto:
On Sat, Sep 07, 2013 at 10:14:04AM +0200, Marco Stornelli wrote:
Hi all,
this is an attempt to include pramfs in mainline. At the moment pramfs
has been included in LTSI kernel. Since last review the code is more
or less the same but, with a really
On Mon, Sep 09, 2013 at 07:06:04PM +0100, Al Viro wrote:
> I like my proposal for the set of primitives better:
>
> static inline bool seqretry_and_lock(seqlock_t *lock, unsigned *seq):
> {
> if ((*seq & 1) || !read_seqretry(lock, *seq))
> return true;
> *seq |= 1;
This allows udev (or more recently systemd-tmpfiles) to create /dev/cuse on
boot, in the same way as /dev/fuse is currently created, and the corresponding
module to be loaded on first access.
The corresponding functionalty was introduced for fuse in commit 578454f.
Signed-off-by: Tom Gundersen
On Mon, Sep 9, 2013 at 11:06 AM, Al Viro wrote:
>>
>> And while the rename sequence lock protects against _renames_, it does
>> not protect against just plain dentries getting free'd under memory
>> pressure.
>
> It protects the chain of ->d_parent, so they'd better not get freeds at
> all...
On 09/08/13 23:16, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any code for v3.13 to your linux-next included branches
> until after v3.12-rc1 is released.
>
> Changes since 20130906:
>
on x86_64:
drivers/built-in.o: In function `ntb_transport_free_queue':
(.text+0x150344):
This allows udev (or more recently systemd-tmpfiles) to create /dev/cuse on
boot, in the same way as /dev/fuse is currently created, and the corresponding
module to be loaded on first access.
The corresponding functionalty was introduced for fuse in commit 578454f.
Signed-off-by: Tom Gundersen
On Mon, Sep 09, 2013 at 10:45:38AM -0700, Linus Torvalds wrote:
> On Mon, Sep 9, 2013 at 10:29 AM, Al Viro wrote:
> >
> > I'm not sure I like mixing rcu_read_lock() into that - d_path() and friends
> > can do that themselves just fine (it needs to be taken when seq is even),
> > and e.g. d_walk()
On Mon, Sep 09, 2013 at 01:55:06PM -0400, Waiman Long wrote:
> >I'm not sure I like mixing rcu_read_lock() into that - d_path() and friends
> >can do that themselves just fine (it needs to be taken when seq is even),
> >and e.g. d_walk() doesn't need it at all. Other than that, I'm OK with
>
On Mon, Sep 09, 2013 at 12:40:44PM -0400, Steven Rostedt wrote:
> On Mon, 9 Sep 2013 09:22:15 -0700
> "Paul E. McKenney" wrote:
> > However, the API we are arguing about is deep within the implementation.
> > It is not at the level of rcu_read_lock(). It is something that should
> > not have
On Mon, Sep 09, 2013 at 01:06:05PM -0400, Steven Rostedt wrote:
> On Mon, 9 Sep 2013 09:58:36 -0700
> "Paul E. McKenney" wrote:
>
>
> > > "rcu_is_ignored()" or "rcu_is_not_active()", "rcu_is_watching_you()"
> >
> > You know, I am strongly tempted by "rcu_is_watching_you()", but I have
> > this
On Mon, Sep 9, 2013 at 10:29 AM, Al Viro wrote:
>
> I'm not sure I like mixing rcu_read_lock() into that - d_path() and friends
> can do that themselves just fine (it needs to be taken when seq is even),
> and e.g. d_walk() doesn't need it at all. Other than that, I'm OK with
> this variant.
On Mon, Sep 09, 2013 at 03:10:10PM +0200, azurIt wrote:
> >Hi azur,
> >
> >On Wed, Sep 04, 2013 at 10:18:52AM +0200, azurIt wrote:
> >> > CC: "Andrew Morton" , "Michal Hocko"
> >> > , "David Rientjes" , "KAMEZAWA
> >> > Hiroyuki" , "KOSAKI Motohiro"
> >> > , linux...@kvack.org,
> >> >
On Wed, Jul 24, 2013 at 03:02:45PM +0100, Ben Hutchings wrote:
> 3.2.49-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Hauke Mehrtens
>
> commit 693026ef2e751fd94d2e6c71028e68343cc875d5 upstream.
>
> When b43 gets build into the kernel
On Mon, Sep 09, 2013 at 06:01:16PM +0200, Paul Chavent wrote:
> Do the same way as in serialcore.c for uart_handle_dcd_change. It
> removes duplicated code around the usb_serial_handle_dcd_change calls.
>
> Signed-off-by: Paul Chavent
> ---
> drivers/usb/serial/ch341.c | 7 ++-
>
On 09/09/2013 01:29 PM, Al Viro wrote:
On Mon, Sep 09, 2013 at 12:18:13PM -0400, Waiman Long wrote:
+/**
+ * read_seqbegin_or_lock - begin a sequence number check or locking block
+ * lock: sequence lock
+ * seq : sequence number to be checked
+ *
+ * First try it once optimistically without
Not using the return value can in the generic case be racy, so it's
in general good practice to check the return value instead.
This also resolved the warning caused on ARM and other architectures:
fs/direct-io.c: In function 'sb_init_dio_done_wq':
fs/direct-io.c:557:2: warning: value computed
On Mon, Sep 09, 2013 at 07:45:23PM +0200, Johan Hovold wrote:
> On Mon, Sep 09, 2013 at 06:01:16PM +0200, Paul Chavent wrote:
> > Do the same way as in serialcore.c for uart_handle_dcd_change. It
> > removes duplicated code around the usb_serial_handle_dcd_change calls.
> >
> > Signed-off-by:
Hello.
On 09/09/2013 08:01 PM, Paul Chavent wrote:
This patch depends on 72df17e... (PATCH 1).
You don't need to say that when you publish the patches as a series. It's
assumed.
It restores the retreiving
of a protected instance of tty. As opposed to the serialcore.c
dcd_change
On Mon, Sep 09, 2013 at 01:29:08PM -0400, Mathieu Desnoyers wrote:
> * Paul E. McKenney (paul...@linux.vnet.ibm.com) wrote:
> > On Mon, Sep 09, 2013 at 12:34:22PM -0400, Steven Rostedt wrote:
> [...]
> > > "rcu_is_ignored()" or "rcu_is_not_active()", "rcu_is_watching_you()"
> >
> > You know, I am
* Paul E. McKenney (paul...@linux.vnet.ibm.com) wrote:
> On Mon, Sep 09, 2013 at 12:34:22PM -0400, Steven Rostedt wrote:
[...]
> > "rcu_is_ignored()" or "rcu_is_not_active()", "rcu_is_watching_you()"
>
> You know, I am strongly tempted by "rcu_is_watching_you()", but I have
> this feeling that it
On Wed, Sep 4, 2013 at 6:22 PM, H. Peter Anvin wrote:
> I think it would be crazy encoding UTC with a non-POSIX scheme.
The whole point is to find a good way to return the time that solves
the problems with the POSIX scheme. Some of the problems, as I see
them, are:
- Performance: seconds +
Hi Linus,
Please pull these XFS updates for 3.12-rc1. Most of this is related to the
libxfs kernel/userspace sync, there is also project quota work, performance
work in the log, recovery, and the CIL. User namespace support has been
added, directory entries now have file type
During the last merge window (3.12) a couple of modules gained devname
aliases, but without the necessary major and minor information. These were
then silently ignored when generating modules.devname.
Complain loudly to avoid such errors sneaking in undetected in the future:
depmod: ERROR:
On 09/09/2013 01:45 PM, Linus Torvalds wrote:
On Mon, Sep 9, 2013 at 10:29 AM, Al Viro wrote:
I'm not sure I like mixing rcu_read_lock() into that - d_path() and friends
can do that themselves just fine (it needs to be taken when seq is even),
and e.g. d_walk() doesn't need it at all. Other
On 9/6/2013 2:50 PM, Olof Johansson wrote:
Hi,
Some comments below.
On Fri, Sep 06, 2013 at 12:32:22PM -0700, Rohit Vaswani wrote:
This patch adds basic board support for APQ8074 Dragonboard
dtb-$(CONFIG_ARCH_MSM) += msm8660-surf.dtb \
- msm8960-cdp.dtb
+ msm8960-cdp.dtb \
+
Oleg Nesterov writes:
> On 09/08, Eric W. Biederman wrote:
>>
>> Oleg Nesterov writes:
>>
>> > On 09/08, Oleg Nesterov wrote:
>> >>
>> >> Off topic. What if the first alloc_pid() succeeds and then later
>> >> copy_process() fails. In this case free_pid() is called but
>> >> PIDNS_HASH_ADDING
On Mon, 9 Sep 2013, Milosz Tanski wrote:
> David,
>
> I guess that's really a better question for Sage. He sent my branch
> (which includes your changes) plus a whole slew of things over to
> Linus. I'm going guess that a small follow on patch is simplest but
> I'll let him comment.
>
> Here's
On Mon, Sep 09, 2013 at 12:18:13PM -0400, Waiman Long wrote:
> +/**
> + * read_seqbegin_or_lock - begin a sequence number check or locking block
> + * lock: sequence lock
> + * seq : sequence number to be checked
> + *
> + * First try it once optimistically without taking the lock. If that fails,
On Mon, 2013-09-09 at 13:18 -0400, valdis.kletni...@vt.edu wrote:
> You may as well bite the bullet on this one, and tie it together. Without
> Secure Boot, by the time your code runs it's already too late. That's the
> whole point of Secure Boot, after all.
It's already been made clear that
On Mon, Sep 2, 2013 at 11:09 AM, Lorenzo Pieralisi
wrote:
> On Thu, Aug 29, 2013 at 06:57:15PM +0100, Olof Johansson wrote:
>> On Thu, Aug 29, 2013 at 06:04:25PM +1000, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Today's linux-next merge of the arm-soc tree got a conflict in
>> >
On Mon, Sep 09, 2013 at 10:08:19AM -0700, Guenter Roeck wrote:
> On Mon, Sep 09, 2013 at 09:39:02AM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Sep 09, 2013 at 06:40:12AM -0700, Christoph Hellwig wrote:
> > > On Sun, Sep 08, 2013 at 06:59:45PM -0700, Greg Kroah-Hartman wrote:
> > > > Can't we
On Mon, 09 Sep 2013 11:49:34 -0400, Matthew Garrett said:
> So, this is my final attempt at providing the functionality I'm interested
> in without inherently tying it to Secure Boot. There's strong parallels
> between the functionality that I'm interested in and the BSD securelevel
> interface,
On Mon, Sep 09, 2013 at 09:55:11AM -0400, Steven Rostedt wrote:
> On Mon, 9 Sep 2013 06:46:05 -0700
> "Paul E. McKenney" wrote:
>
>
> > > Also, if its per-task, why don't we have this in the task struct? The
> > > current scheme makes the context switch more expensive -- is this the
> > > right
On Mon, Sep 09, 2013 at 10:44:03AM +0930, Rusty Russell wrote:
> Kyle McMartin writes:
> > On Fri, Sep 06, 2013 at 07:51:18PM +0200, Frantisek Hrbata wrote:
> >> > > v2: - reuse mod->ctors for .init_array section for modules, because
> >> > > gcc uses
> >> > > .ctors or .init_array, but
On Mon, Sep 09, 2013 at 06:01:19PM +0200, Paul Chavent wrote:
> In order to have the PPS line discipline to work with usb devices.
>
> Signed-off-by: Paul Chavent
> ---
> drivers/usb/serial/generic.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/usb/serial/generic.c
On 09/09/2013 08:49 AM, Matthew Garrett wrote:
> Provide a coarse-grained runtime configuration option for restricting
> userspace's ability to modify the running kernel.
>
> Signed-off-by: Matthew Garrett
> ---
> Documentation/security/securelevel.txt | 23 +++
> include/linux/security.h
On Mon, Sep 09, 2013 at 05:53:19PM +0200, David Herrmann wrote:
> On Fri, Jul 12, 2013 at 10:23 PM, Adam Borowski wrote:
> > drivers/tty/vt/vt.c | 26 --
> > 1 file changed, 20 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
>
Hi Tom
On Mon, Sep 9, 2013 at 5:43 PM, Tom Gundersen wrote:
> Hi Marcel,
>
> The above commit (60cbd53 in mainline) doesn't appear to work for me.
> I.e., depmod does not create an entry in modules.devname and hence no
> device node is created on boot.
>
> If I understand correctly, you'd also
On Mon, 9 Sep 2013 09:22:15 -0700
"Paul E. McKenney" wrote:
> However, the API we are arguing about is deep within the implementation.
> It is not at the level of rcu_read_lock(). It is something that should
> not have that many invocations -- after all, the things using it are
> binding
On Mon, Sep 09, 2013 at 04:21:55PM +0200, Peter Zijlstra wrote:
> On Mon, Sep 09, 2013 at 06:23:43AM -0700, Paul E. McKenney wrote:
> > Peter, in the general case, you are quite correct. But this is a special
> > case where it really does work.
> >
> > The key point here is that preemption and
On Mon, 9 Sep 2013 09:09:20 -0700
"Paul E. McKenney" wrote:
> Oddly enough, the earliest implementations of RCU that I worked with
> back in the early 1990s had implementation but no concept. The concepts
> came later. Something about how dragging people through 1500 lines
> of highly
On Mon, 9 Sep 2013 09:58:36 -0700
"Paul E. McKenney" wrote:
> > "rcu_is_ignored()" or "rcu_is_not_active()", "rcu_is_watching_you()"
>
> You know, I am strongly tempted by "rcu_is_watching_you()", but I have
> this feeling that it is too cute for its own good. ;-)
Sign of the times...
On Fri, Sep 06, 2013 at 01:16:45PM +0800, Weijie Yang wrote:
> zswap_tree is not freed when swapoff, and it got re-kmalloc in swapon,
> so memory-leak occurs.
>
> Modify: free memory of zswap_tree in zswap_frontswap_invalidate_area().
>
> Signed-off-by: Weijie Yang
> ---
> mm/zswap.c |4
201 - 300 of 1474 matches
Mail list logo
