When export root dir(/) via nfs, and mount a particular dir under root, eg
/nfsexport, there will be defect double slash output in /proc/mounts, like
localhost://nfsexport. While this patch change it to localhost:/nfsexport.
Signed-off-by: Xiong Zhou
---
fs/nfs/namespace.c | 2 +-
1 file
[ 220.262245] Call Trace:
[ 220.262252] [] load_balance+0x156/0x980
[ 220.262259] [] ? _raw_spin_unlock_irqrestore+0x2e/0xa0
[ 220.262266] [] idle_balance+0xe3/0x150
[ 220.262270] [] __schedule+0x797/0x8d0
[ 220.262277] [] schedule+0x24/0x70
[ 220.262283] []
On Thu, Aug 21, 2014 at 05:19:46PM -0500, Aravind Gopalakrishnan wrote:
> @@ -767,17 +750,25 @@ static void read_dct_base_mask(struct amd64_pvt *pvt)
> int reg1 = DCSB1 + (cs * 4);
> u32 *base0 = >csels[0].csbases[cs];
> u32 *base1 =
于 14-8-15 下午2:07, Borislav Petkov 写道:
On Fri, Aug 15, 2014 at 11:00:42AM +0800, Wanpeng Li wrote:
Is it ok for you to apply this patch or still need update?
Just be patient: we have the merge window still open and after that
kernel summit coming up first.
Thanks for pointing out.
Regards,
On Thu, 2014-08-21 at 22:19 -0400, Pranith Kumar wrote:
> Fix the following build error:
>
> drivers/edac/ppc4xx_edac.c: In function 'mfsdram':
> drivers/edac/ppc4xx_edac.c:249: error: implicit declaration of function
> '__mfdcri'
> drivers/edac/ppc4xx_edac.c: In function 'mtsdram':
>
On Mon, Aug 25, 2014 at 02:51:33PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140823:
>
> The mfd tree still had its build failure so I used the version from
> next-20140822.
>
> The pwm tree last its build failure.
>
> The staging tree still had its build failure for which I
When an AUDIT_GET_FEATURE message is sent from userspace to the kernel, it
should reply with a message tagged as an AUDIT_GET_FEATURE type with a struct
audit_feature. The current reply is a message tagged as an AUDIT_GET
type with a struct audit_feature.
This appears to have been a
--
Szanowny konto uzytkownika e-mail,
Niedawno wykryto nietypowe dzialania z konta e-mail, wiec skrzynka
pocztowa zostala czasowo zawieszona przez administratora systemu, nalezy
odzyskac swoje konto, klikajac na ponizszy link lub skopiuj do przegladarki:
--
Szanowny konto uzytkownika e-mail,
Niedawno wykryto nietypowe dzialania z konta e-mail, wiec skrzynka
pocztowa zostala czasowo zawieszona przez administratora systemu, nalezy
odzyskac swoje konto, klikajac na ponizszy link lub skopiuj do przegladarki:
On Sat, Aug 23, 2014 at 08:04:22AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140822:
>
> The mfd tree gained a build failure so I used the version from
> next-20140822.
>
> The usb-gadget tree gained a conflict against the usb-gadget-fixes tree.
>
> The pwm tree gained a
Hi all,
Changes since 20140823:
The mfd tree still had its build failure so I used the version from
next-20140822.
The pwm tree last its build failure.
The staging tree still had its build failure for which I applied a
fix patch.
Non-merge commits (relative to Linus' tree): 1539
1489 files
On Sun, Aug 24, 2014 at 11:40:50PM -0400, David Horner wrote:
> On Sun, Aug 24, 2014 at 7:56 PM, Minchan Kim wrote:
> > Hello David,
> >
> > On Fri, Aug 22, 2014 at 06:55:38AM -0400, David Horner wrote:
> >> On Thu, Aug 21, 2014 at 8:42 PM, Minchan Kim wrote:
> >> > Since zram has no control
From: Hayes Wang
Date: Mon, 25 Aug 2014 03:43:04 +
> From: David Miller [mailto:da...@davemloft.net]
> [...]
>> You haven't told us why you need to do this.
>>
>> These are just programming registers in the chip, and I see no reason
>> to not keep these in the driver with real code.
>>
Chris,
On Sat, Aug 23, 2014 at 3:29 AM, Chris Zhong wrote:
> rk808.txt: Add device tree bindings for rockchip's rk808 pmic.
>
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v4:
> Adviced by doug
> - add "clock-output-names" propertiey
> - add a header file "rockchip,rk808.h"
>
> Changes in
On Thu, 2014-08-21 at 10:51 -0500, Robert Jennings wrote:
> On 08/20/2014 11:41 PM, Michael Ellerman wrote:
> > On Wed, 2014-08-13 at 14:48 +0530, Himangi Saraogi wrote:
> >> Continue is not needed at the bottom of a loop.
> >
> > True.
> >
> > I wonder though, is the code trying to continue to
On Mon, Aug 25, 2014 at 11:30:59AM +0800, Xiubo Li wrote:
> Signed-off-by: Xiubo Li
> ---
> sound/soc/fsl/fsl_asrc.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/sound/soc/fsl/fsl_asrc.c b/sound/soc/fsl/fsl_asrc.c
> index 8221104..3b14531 100644
> ---
Chris,
On Sat, Aug 23, 2014 at 7:57 AM, Mark Brown wrote:
> On Sat, Aug 23, 2014 at 07:04:50PM +0800, Chris Zhong wrote:
>> The regulator module consists of 4 DCDCs, 8 LDOs and 2 switches.
>> The output voltages are configurable and are meant to supply power
>> to the main processor and other
On Sun, Aug 24, 2014 at 8:05 PM, Minchan Kim wrote:
> zs_get_total_size_bytes returns a amount of memory zsmalloc
> consumed with *byte unit* but zsmalloc operates *page unit*
> rather than byte unit so let's change the API so benefit
> we could get is that reduce unnecessary overhead
> (ie,
On Sun, Aug 24, 2014 at 8:05 PM, Minchan Kim wrote:
> Normally, zram user could get maximum memory usage zram consumed
> via polling mem_used_total with sysfs in userspace.
>
> But it has a critical problem because user can miss peak memory
> usage during update inverval of polling. For avoiding
Chris,
On Sat, Aug 23, 2014 at 4:07 AM, Chris Zhong wrote:
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v4:
Wait, is this v4 or v3? The subject line still says v3, which is confusing.
> Advices by Doug
> - add a "#clock-cells" propertiy
> - update the example
>
> Changes in v3: None
On 2014年08月25日 11:13, Linus Torvalds wrote:
> On Sun, Aug 24, 2014 at 7:53 PM, Lan Tianyu wrote:
>>
>> Sorry about this. We are resolving the issue in the other bug
>> report(https://lkml.org/lkml/2014/8/21/606) and I have proposed a fix
>> patch(http://marc.info/?l=linux-acpi=140869309231199=2).
From: David Miller [mailto:da...@davemloft.net]
[...]
> You haven't told us why you need to do this.
>
> These are just programming registers in the chip, and I see no reason
> to not keep these in the driver with real code.
>
> I'm not applying this series, you haven't explained what is
On Sun, Aug 24, 2014 at 7:56 PM, Minchan Kim wrote:
> Hello David,
>
> On Fri, Aug 22, 2014 at 06:55:38AM -0400, David Horner wrote:
>> On Thu, Aug 21, 2014 at 8:42 PM, Minchan Kim wrote:
>> > Since zram has no control feature to limit memory usage,
>> > it makes hard to manage system memrory.
Signed-off-by: Xiubo Li
---
Documentation/devicetree/bindings/sound/fsl-sai.txt | 7 +++
sound/soc/fsl/fsl_sai.c | 6 +-
sound/soc/fsl/fsl_sai.h | 1 -
3 files changed, 4 insertions(+), 10 deletions(-)
diff --git
Signed-off-by: Xiubo Li
---
sound/soc/fsl/fsl_spdif.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/sound/soc/fsl/fsl_spdif.c b/sound/soc/fsl/fsl_spdif.c
index 70acfe4..ae4e408 100644
--- a/sound/soc/fsl/fsl_spdif.c
+++ b/sound/soc/fsl/fsl_spdif.c
@@ -1040,7 +1040,7 @@
Signed-off-by: Xiubo Li
---
sound/soc/fsl/fsl_esai.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/sound/soc/fsl/fsl_esai.c b/sound/soc/fsl/fsl_esai.c
index b2f6b3e..8bcdfda 100644
--- a/sound/soc/fsl/fsl_esai.c
+++ b/sound/soc/fsl/fsl_esai.c
@@ -710,7 +710,7 @@ static
Signed-off-by: Xiubo Li
---
sound/soc/fsl/fsl_asrc.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/sound/soc/fsl/fsl_asrc.c b/sound/soc/fsl/fsl_asrc.c
index 8221104..3b14531 100644
--- a/sound/soc/fsl/fsl_asrc.c
+++ b/sound/soc/fsl/fsl_asrc.c
@@ -684,7 +684,7 @@ static
Changes in V3:
- Delete 'ASoC: fsl-sai: rename big_endian_data to is_msb_first.' patch.
Changes in V2:
- Modified the regmap config to const type.
- Added ASRC patch.
- Followed Rutland's advice.
Xiubo Li (4):
ASoC: fsl-asrc: Convert to use regmap framework's endianness method.
ASoC:
For VMAs that don't want write notifications, PTEs created for read
faults have their write bit set. If the read fault happens after
VM_SOFTDIRTY is cleared, then the PTE's softdirty bit will remain
clear after subsequent writes.
Here's a simple code snippet to demonstrate the bug:
char* m =
Francois Romieu [mailto:rom...@fr.zoreil.com]
[...]
> > +static void rtl_request_firmware(struct r8152 *tp)
> > +{
> > + char *fw_name = NULL;
> > +
> > + if (tp->rtl_fw.fw)
> > + goto out_request;
> > +
> > + switch (tp->version) {
> > + case RTL_VER_01:
> > + fw_name
On Mon, Aug 25, 2014 at 7:14 AM, Wanpeng Li wrote:
> Please Cc kvm ml.
You've done that for me, thanks. The page-walk length sanity check has
been done in the hardware_setup() function, so it's not necessary in
this patch, but I still think it does make sense for the memory type
check, any
On Sun, Aug 24, 2014 at 5:38 PM, Gleb Natapov wrote:
> On Sun, Aug 24, 2014 at 11:54:32AM +0800, Dennis Chen wrote:
>> This patch is used to construct the eptp in vmx mode with values
>> readed from MSR according to the intel x86 software developer's
>> manual.
>>
>> static u64
On Sun, Aug 24, 2014 at 7:53 PM, Lan Tianyu wrote:
>
> Sorry about this. We are resolving the issue in the other bug
> report(https://lkml.org/lkml/2014/8/21/606) and I have proposed a fix
> patch(http://marc.info/?l=linux-acpi=140869309231199=2).
Ahh. Good. That patch looks fine to me, and
On 08/24/2014 07:14 PM, Michael S. Tsirkin wrote:
> On Fri, Aug 22, 2014 at 07:52:22AM -0400, Pankaj Gupta wrote:
>>> On 08/20/2014 07:17 PM, Michael S. Tsirkin wrote:
On Wed, Aug 20, 2014 at 12:58:17PM +0200, Jiri Pirko wrote:
>> Mon, Aug 18, 2014 at 03:37:18PM CEST, pagu...@redhat.com
On 2014年08月25日 01:50, Linus Torvalds wrote:
> Rafael? Lan Tianyu? This is not some minor locking bug. This is a
> *major* mistake unless I misread something.
>
Hi Linus:
Sorry about this. We are resolving the issue in the other bug
report(https://lkml.org/lkml/2014/8/21/606) and I have proposed
On 08/22/2014 10:16 PM, Eric Dumazet wrote:
> On Fri, 2014-08-22 at 17:08 +0800, Jason Wang wrote:
>
>> > But this is just for current process. We want to determine whether or
>> > not it was worth to loop busily in current process by checking if
>> > there's any another runnable processes or
Hi Dmitry,
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Saturday, August 23, 2014 7:55 AM
> To: Dudley Du
> Cc: Rafael J. Wysocki; Benson Leung; Patrik Fimml;
> linux-in...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Dudley Du
> Subject:
Hi Dmitry,
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: Saturday, August 23, 2014 7:52 AM
> To: Dudley Du
> Cc: Rafael J. Wysocki; Benson Leung; Patrik Fimml;
> linux-in...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Dudley Du
> Subject:
On 08/20/2014 05:21 PM, Lee Jones wrote:
On Wed, 20 Aug 2014, Chris Zhong wrote:
The RK808 chip is a power management IC for multimedia and handheld
devices. It contains the following components:
- Regulators
- RTC
The rk808 core driver is registered as a platform driver and provides
On 2014/8/23 6:16, Andrew Morton wrote:
> On Mon, 18 Aug 2014 11:25:36 +0800 Zhang Zhen
> wrote:
>
>> On 2014/8/16 5:37, Toshi Kani wrote:
>>> On Wed, 2014-08-13 at 12:10 +0800, Zhang Zhen wrote:
Currently memory-hotplug has two limits:
1. If the memory block is in ZONE_NORMAL, you
The "dev" has been deleted from "struct rk808" in rk808 mfd driver v4,
so rk808->dev should be replaced >dev here.
Signed-off-by: Chris Zhong
---
drivers/regulator/rk808-regulator.c | 34 ++
1 file changed, 14 insertions(+), 20 deletions(-)
diff --git
On Sat, 23 Aug 2014, Oleg Nesterov wrote:
> On 08/23, Cyrill Gorcunov wrote:
> >
> > On Sat, Aug 23, 2014 at 04:43:27PM +0200, Oleg Nesterov wrote:
> > > The ->start_stack check in do_shmat() looks ugly and simply wrong.
> > >
> > > 1. ->start_stack is only valid right after exec(), the
From: Dariusz Marcinkiewicz
Date: Sun, 24 Aug 2014 20:40:16 +0200
> This cuts down the number of debug information spit out by
> the driver.
>
> Signed-off-by: Dariusz Marcinkiewicz
Applied, thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, 18 Aug 2014 19:07:20 +0530
Pankaj Gupta wrote:
> Networking under kvm works best if we allocate a per-vCPU RX and TX
> queue in a virtual NIC. This requires a per-vCPU queue on the host side.
>
> It is now safe to increase the maximum number of queues.
> Preceding patches:
> net:
On Mon, 18 Aug 2014 19:07:19 +0530
Pankaj Gupta wrote:
> This patch switches to flex array to implement the flow caches, it brings
> several advantages:
>
> - Reduce the size of the tun_struct structure, which allows us to increase the
> upper limit of queues in future.
> - Avoid higher order
Hi Linus,
Please consider these SH drivers updates for v3.17.
I realise these are slightly late in the rc cycle so
please don't hesitate to ask me to defer them to v3.18.
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
From: Geert Uytterhoeven
Currently the sh-intc driver is compiled on all SuperH and
non-multiplatform SH-Mobile platforms, while it's only used on a limited
number of platforms:
- SuperH: SH2(A), SH3(A), SH4(A)(L) (all but SH5)
- ARM: sh7372, sh73a0
Drop the "default y" on SH_INTC, make all
Dear Andrew,
On 08/23/2014 05:42 AM, Andrew Morton wrote:
> On Tue, 12 Aug 2014 11:01:07 +0900 y...@samsung.com wrote:
>
>> This patch define s3c_rtc structure including necessary variables for S3C RTC
>> device instead of global variables. This patch improves the readability by
>> removing
In analogy with commits 5af84b82701a and 97df8c12995,
using asynchronous threads can improve the overall
resume time significantly.
This patch is for dpm_complete phase.
Signed-off-by: Chuansheng Liu
Signed-off-by: xiaoming wang
---
drivers/base/power/main.c | 38
In analogy with commits 5af84b82701a and 97df8c12995,
using asynchronous threads can improve the overall
suspend time significantly.
This patch is for dpm_prepare phase.
Signed-off-by: Chuansheng Liu
Signed-off-by: xiaoming wang
---
drivers/base/power/main.c | 57
From: Alexei Starovoitov
Date: Sun, 24 Aug 2014 13:21:01 -0700
> enough RFCs, let's finalize it...
Please break this down into smaller, easier to review, sets
of changes.
Asking people to review nearly 30 patches at once isn't reasonable.
Shoot for something like about 10 at a time, at most.
Hello Chao,
On Fri, Aug 22, 2014 at 04:21:01PM +0800, Chao Yu wrote:
> Since we have supported handling discard request in this commit
> f4659d8e620d08bd1a84a8aec5d2f5294a242764 (zram: support REQ_DISCARD), zram got
> one more chance to free unused memory whenever received discard request. But
>
مرحبا عزيزتي
اسمي روز كرون، سيدة المحبة والرعاية، حصلت البريد الالكتروني الخاص بك اليوم
عندما كنت
تصفح تبحث عن شريك صادقين، وأنا أشعر لإسقاط هذا قليل خط لكم،
يرجى الاتصال لي مع هذا عنوان البريد الإلكتروني (rosecar...@outlook.com)
حتى أستطيع أن اقول لكم المزيد عن نفسي ويرسل لك صوري
مع الحب وقبلة
Barclays Bank PLC
28 High Street
Nottinghamshire
Storbritannien
NG1 2bd
martinsjohn...@gmail.com
Kära vän,
Mitt namn är John k. Martins och jag chefstjänsteman Barclays bank
nottingham, Storbritannien. Jag är gift med 3 barn.
Jag vill informera er om att jag behöver din brådskande hjälp.
Normally, zram user could get maximum memory usage zram consumed
via polling mem_used_total with sysfs in userspace.
But it has a critical problem because user can miss peak memory
usage during update inverval of polling. For avoiding that,
user should poll it with shorter interval(ie,
zs_get_total_size_bytes returns a amount of memory zsmalloc
consumed with *byte unit* but zsmalloc operates *page unit*
rather than byte unit so let's change the API so benefit
we could get is that reduce unnecessary overhead
(ie, change page unit with byte unit) in zsmalloc.
Since return type is
pages_allocated has counted in size_class structure and when user
of zsmalloc want to see total_size_bytes, it should gather all of
count from each size_class to report the sum.
it's not bad if user don't see the value often but if user start
to see the value frequently, it would be not a good
Since zram has no control feature to limit memory usage,
it makes hard to manage system memrory.
This patch adds new knob "mem_limit" via sysfs to set up the
a limit so that zram could fail allocation once it reaches
the limit.
In addition, user could change the limit in runtime so that
he could
On Tue, Aug 19, 2014 at 9:30 PM, Valentina Manea
wrote:
> At this point, USB/IP userspace code is fully functional
> and can be moved out of staging.
>
> Signed-off-by: Valentina Manea
Bumping this in case Greg missed the patch series.
Valentina
--
To unsubscribe from this list: send the line
Currently, zram has no feature to limit memory so theoretically
zram can deplete system memory.
Users have asked for a limit several times as even without exhaustion
zram makes it hard to control memory usage of the platform.
This patchset adds the feature.
Patch 1 makes zs_get_total_size_bytes
On Sun, Aug 24, 2014 at 3:58 PM, Linus Torvalds
wrote:
> On Sun, Aug 24, 2014 at 11:40 AM, Olof Johansson wrote:
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git fixes
>
> Grr. Yes and no.
>
> You didn't really mean for me to
On Sat, Aug 23, 2014 at 10:40:14AM -0700, Randy Dunlap wrote:
> On 08/23/14 02:31, Fejes József wrote:
> > Hi,
> >
> > I think there's a problem with commit
> > 6b8f0c8780c71d78624f736d7849645b64cc88b7: config IOSF_MBI is
> > automatically a module and I cannot change that.
> >
> > I've been
Hello Dan,
On Fri, Aug 22, 2014 at 03:15:36PM -0400, Dan Streetman wrote:
> On Thu, Aug 21, 2014 at 8:42 PM, Minchan Kim wrote:
> > Currently, zram has no feature to limit memory so theoretically
> > zram can deplete system memory.
> > Users have asked for a limit several times as even without
Hello David,
On Fri, Aug 22, 2014 at 06:55:38AM -0400, David Horner wrote:
> On Thu, Aug 21, 2014 at 8:42 PM, Minchan Kim wrote:
> > Since zram has no control feature to limit memory usage,
> > it makes hard to manage system memrory.
> >
> > This patch adds new knob "mem_limit" via sysfs to set
On Sat, Aug 23, 2014 at 11:14 AM, Olof Johansson wrote:
> On Sat, Aug 23, 2014 at 03:56:42PM +0200, Arnd Bergmann wrote:
>> On Saturday 23 August 2014, Olof Johansson wrote:
>> > On Fri, Aug 22, 2014 at 02:10:23PM -0700, Andrew Bresticker wrote:
>> > > On Fri, Aug 22, 2014 at 1:42 PM, Florian
Fix checkpatch.pl spaces required around that '<' errors
Signed-off-by: Greg Donald
---
drivers/staging/rtl8821ae/btcoexist/halbtc8723b2ant.c | 2 +-
drivers/staging/rtl8821ae/rtl8821ae/phy.c | 18 +-
drivers/staging/rtl8821ae/rtl8821ae/rf.c | 2 +-
3
On Fri, Aug 22, 2014 at 8:06 AM, Liviu Dudau wrote:
> On Thu, Aug 21, 2014 at 11:08:48PM -0500, Rob Herring wrote:
>> On Tue, Aug 12, 2014 at 11:25 AM, Liviu Dudau wrote:
>> > The ranges property for a host bridge controller in DT describes
>> > the mapping between the PCI bus address and the
Please Cc kvm ml.
On Sun, Aug 24, 2014 at 11:54:32AM +0800, Dennis Chen wrote:
>This patch is used to construct the eptp in vmx mode with values
>readed from MSR according to the intel x86 software developer's
>manual.
>
>Signed-off-by: Dennis Chen
>---
> arch/x86/include/asm/vmx.h |1 +
>
On 08/24/2014 02:11 PM, Richard Weinberger wrote:
> Am 23.08.2014 19:43, schrieb Thorsten Knabe:
>> Hi Richard.
>>
>> On 08/23/2014 05:34 PM, Richard Weinberger wrote:
>>> Hi!
>>>
>>> Am 23.08.2014 15:47, schrieb Thorsten Knabe:
From: Thorsten Knabe
UML: UBD: Fix for processes
On Sun, Aug 24, 2014 at 11:40 AM, Olof Johansson wrote:
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git fixes
Grr. Yes and no.
You didn't really mean for me to pull that branch, you meant for me to
pull your tag "fixes-for-linus".
Fix checkpatch.pl switch and case should be at the same indent errors
Signed-off-by: Greg Donald
---
drivers/staging/rtl8192u/r8192U_core.c | 510 -
1 file changed, 252 insertions(+), 258 deletions(-)
diff --git a/drivers/staging/rtl8192u/r8192U_core.c
Any attempt to look up a pathname that passes though an
autofs4 mount is currently forced out of RCU-walk into
REF-walk.
This can significantly hurt performance of many-thread work
loads on many-core systems, especially if the automounted
filesystem supports RCU-walk but doesn't get to benefit
Have a "test" function change the value it is testing can
be confusing, particularly as a future patch will be calling
this function twice.
So move the update for 'last_used' to avoid repeat expiry
to the place where the final determination on what to expire is known.
Reviewed-by: Ian Kent
Future patch will potentially call this twice, so make it
separate.
Reviewed-by: Ian Kent
Tested-by: Ian Kent
Signed-off-by: NeilBrown
---
fs/autofs4/expire.c | 162 ---
1 file changed, 88 insertions(+), 74 deletions(-)
diff --git
->fs_lock protects AUTOFS_INF_EXPIRING. We need to be sure
that once the flag is set, no new references beneath the dentry
are taken. So rcu-walk currently needs to take fs_lock before
checking the flag. This hurts performance.
Change the expiry to a two-stage process.
First set
This documents autofs from the perspective of what the module actually
supports rather than how automount is expected to use it.
It is formatted using "markdown" and works best with Markdown.pl
(markdown_py doesn't like some constructs).
Copy-edited-by: Randy Dunlap
Signed-off-by: NeilBrown
If rcu-walk mode we don't *have* to return -EISDIR for non-mount-traps
as we will simply drop into REF-walk and handling DCACHE_NEED_AUTOMOUNT
dentrys the slow way. But it is better if we do when possible.
In 'oz_mode', use the same condition as ref-walk: if not a mountpoint,
then it must be
Hi Andrew,
this series teaches autofs about RCU-walk so that we don't drop
straight into REF-walk when we hit an autofs directory, and so that
we avoid spinlocks as much as possible when performing an RCU-walk.
This is needed so that the benefits of the recent NFS support for
RCU-walk are
From: Eric Paris
This is to be used to audit by executable rules, but audit watches
should be able to share this code eventually.
At the moment the audit watch code is a lot more complex, that code only
creates one fsnotify watch per parent directory. That 'audit_parent' in
turn has a list of
Make this interface consistent with watch and filter key, avoiding the extra
string copy and simply consume the new string pointer.
Signed-off-by: Richard Guy Briggs
---
kernel/audit_exe.c |5 -
kernel/audit_fsnotify.c | 12 ++--
kernel/auditfilter.c|2 +-
3 files
From: Eric Paris
Instead of just hard coding the ino and dev of the executable we care
about at the moment the rule is inserted into the kernel, use the new
audit_fsnotify infrastructure. This means that if the inode in question
is unlinked and creat'd (aka updated) the rule will just continue
This is a part of Peter Moody, my and Eric Paris' work to implement
audit by executable name.
Please see the accompanying userspace patch:
https://www.redhat.com/archives/linux-audit/2014-May/msg00019.html
The userspace interface is not expected to change appreciably unless something
From: Eric Paris
This patch implements the ability to filter on the executable. It is
clearly incomplete! This patch adds the inode/dev of the executable at
the moment the rule is loaded. It does not update if the executable is
updated/moved/whatever. That should be added. But at this
On Thu, Jul 17, 2014 at 02:53:48PM +0800, Dudley Du wrote:
> Based on the cyapa core, add the gen3 trackpad device's basic functions
> supported, so gen3 trackpad device can work with kernel input system.
> The basic function is absolutely same as previous cyapa driver only
> support gen3 trackpad
Hi Dudley,
On Thu, Jul 17, 2014 at 02:52:36PM +0800, Dudley Du wrote:
> Add read_fw and raw_data debugfs interfaces for easier issues location
> and collection when report by user.
> TEST=test on Chromebooks.
>
> Signed-off-by: Dudley Du
> ---
> drivers/input/mouse/cyapa.c | 219
>
Hi,
W dniu 20.08.2014 o 19:03, mathieu.poir...@linaro.org pisze:
> From: Mathieu Poirier
>
> Currently supporting ETM and ETB. Support for TPIU
> and SDTI are yet to be added.
Did you tried running the drivers on board or are there any special
preparation needed?
I've BeagleBoard-xM Rev. C
The deprecation warnings for the scan_unevictable interface triggers
by scripts doing `sysctl -a | grep something else'. This is annoying
and not helpful.
The interface has been defunct since 264e56d8247e ("mm: disable user
interface to manually rescue unevictable pages"), which was in 2011,
and
Hayes Wang :
> diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
> index 937d132..63542cc 100644
> --- a/drivers/net/usb/r8152.c
> +++ b/drivers/net/usb/r8152.c
[...]
> +static void rtl_request_firmware(struct r8152 *tp)
> +{
> + char *fw_name = NULL;
> +
> + if
This patch works on my hardware. Xorg starts up fine with fbdev now.
Thanks for the fix!
--Günther
Daniel Kurtz writes:
> Commit [0] stopped setting fix.smem_start and fix.smem_len when creating
> the fbdev.
>
> [0] 2f1eab8d8ab59e799f7d51d62410b398607a7bc3
> drm/exynos/fbdev: don't set
On Fri, Aug 22, 2014 at 12:39:59AM +, Elliott, Robert (Server Storage)
wrote:
> If you trigger hundreds of errors (e.g., hot remove a device
> during heavy IO), then all the prints to the linux serial console
> bog down the system, causing timeouts in commands to other
> devices and soft
On 08/24/2014 07:49 AM, Ingo Molnar wrote:
> >> + buf_left = buf_len;
> >> + for (i = 0; i < ARRAY_SIZE(perfomance_killing_configs); i++) {
> >> + buf_written += snprintf(buf + buf_written, buf_left,
> >> + "%s%s\n",
From: Colin Ian King
Originally found by cppcheck:
[arch/arm64/crypto/sha2-ce-glue.c:153]: (warning) Assignment of
function parameter has no effect outside the function. Did you
forget dereferencing it?
Updating data by blocks * SHA256_BLOCK_SIZE at the end of
ha2_finup is redundant code
On 14/08/23, Eric W. Biederman wrote:
> Richard Guy Briggs writes:
>
> > Generate and assign a serial number per namespace instance since boot.
> >
> > Use a serial number per namespace (unique across one boot of one kernel)
> > instead of the inode number (which is claimed to have had the right
add BPF_LD_IMM64 instruction to load 64-bit immediate value into a register.
All previous instructions were 8-byte. This is first 16-byte instruction.
Two consecutive 'struct bpf_insn' blocks are interpreted as single instruction:
insn[0].code = BPF_LD | BPF_DW | BPF_IMM
insn[0].dst_reg =
'shift by register' operations are supported by eBPF interpreter, but were
accidently left out of x64 JIT compiler. Fix it and add a testcase.
Signed-off-by: Alexei Starovoitov
---
arch/x86/net/bpf_jit_comp.c | 42 ++
lib/test_bpf.c | 38
'maps' is a generic storage of different types for sharing data between kernel
and userspace.
The maps are accessed from user space via BPF syscall, which has commands:
- create a map with given type and attributes
fd = bpf_map_create(map_type, struct nlattr *attr, int len)
returns fd or
done as separate commit to ease conflict resolution
Signed-off-by: Alexei Starovoitov
---
arch/x86/syscalls/syscall_32.tbl |1 +
arch/x86/syscalls/syscall_64.tbl |1 +
include/linux/syscalls.h |3 ++-
include/uapi/asm-generic/unistd.h |4 +++-
kernel/sys_ni.c
BPF syscall is a demux for different BPF releated commands.
'maps' is a generic storage of different types for sharing data between kernel
and userspace.
The maps can be created from user space via BPF syscall:
- create a map with given type and attributes
fd = bpf_map_create(map_type, struct
add new map type: BPF_MAP_TYPE_HASH
and its simple (not auto resizeable) hash table implementation
Signed-off-by: Alexei Starovoitov
---
include/uapi/linux/bpf.h |1 +
kernel/bpf/Makefile |2 +-
kernel/bpf/hashtab.c | 372 ++
3 files
eBPF programs are safe run-to-completion functions with load/unload
methods from userspace similar to kernel modules.
User space API:
- load eBPF program
fd = bpf_prog_load(bpf_prog_type, struct nlattr *prog, int len)
where 'prog' is a sequence of sections (TEXT, LICENSE)
TEXT - array of
1 - 100 of 456 matches
Mail list logo
