netfilter uses multiple FWINV #defines with identical form that hide a
specific structure variable and dereference it with a invflags member.
$ git grep "#define FWINV"
include/linux/netfilter_bridge/ebtables.h:#define FWINV(bool,invflg) ((bool) ^
!!(info->invflags & invflg))
netfilter uses multiple FWINV #defines with identical form that hide a
specific structure variable and dereference it with a invflags member.
$ git grep "#define FWINV"
include/linux/netfilter_bridge/ebtables.h:#define FWINV(bool,invflg) ((bool) ^
!!(info->invflags & invflg))
On Fri, Jun 24, 2016 at 12:27:27PM -0600, Jason Gunthorpe wrote:
> On Tue, Jun 21, 2016 at 06:10:28PM -0700, Ed Swierk wrote:
>
> > if (chip->ops->req_canceled(chip, status)) {
> > dev_err(chip->pdev, "Operation Canceled\n");
> > +
On Fri, Jun 24, 2016 at 12:27:27PM -0600, Jason Gunthorpe wrote:
> On Tue, Jun 21, 2016 at 06:10:28PM -0700, Ed Swierk wrote:
>
> > if (chip->ops->req_canceled(chip, status)) {
> > dev_err(chip->pdev, "Operation Canceled\n");
> > +
Hi Linus,
Please pull hwmon fixes for Linux v4.7-rc5 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.7-rc5
Thanks,
Guenter
--
The following changes since commit 2744d2fde00dc8bcc3679eb72c81a63058e90faa:
hwmon: (dell-smm)
On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> Hi Jason,
>
> On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > > if (expected > count) {
> > > + dev_err(chip->pdev, "Response too long (wanted
On Fri, Jun 24, 2016 at 11:21:31PM +0300, Jarkko Sakkinen wrote:
> Hi Jason,
>
> On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > > if (expected > count) {
> > > + dev_err(chip->pdev, "Response too long (wanted
Hi Linus,
Please pull hwmon fixes for Linux v4.7-rc5 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.7-rc5
Thanks,
Guenter
--
The following changes since commit 2744d2fde00dc8bcc3679eb72c81a63058e90faa:
hwmon: (dell-smm)
On 06/24, Michal Hocko wrote:
>
> On Fri 24-06-16 16:05:58, Michal Hocko wrote:
> > On Thu 23-06-16 20:52:21, Oleg Nesterov wrote:
> > >
> > > But I agree, this is fixable (and in fact I still hope TIF_MEMDIE will
> > > die,
> > > at least in its current form).
> >
> > We can move the flag to the
On 06/24, Michal Hocko wrote:
>
> On Fri 24-06-16 16:05:58, Michal Hocko wrote:
> > On Thu 23-06-16 20:52:21, Oleg Nesterov wrote:
> > >
> > > But I agree, this is fixable (and in fact I still hope TIF_MEMDIE will
> > > die,
> > > at least in its current form).
> >
> > We can move the flag to the
Hi Jason,
On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > if (expected > count) {
> > + dev_err(chip->pdev, "Response too long (wanted %zd, got %d)\n",
> > + count, expected);
>
> This all
Hi Jason,
On Fri, Jun 24, 2016 at 12:25:15PM -0600, Jason Gunthorpe wrote:
> > expected = be32_to_cpu(*(__be32 *) (buf + 2));
> > if (expected > count) {
> > + dev_err(chip->pdev, "Response too long (wanted %zd, got %d)\n",
> > + count, expected);
>
> This all
On Fri, 17 Jun 2016 15:32:20 +0200 Vlastimil Babka wrote:
> On 06/17/2016 09:57 AM, js1...@gmail.com wrote:
> > From: Sudip Mukherjee
> >
> > We have dereferenced page_ext before checking it. Lets check it first
> > and then used it.
> >
> > Link:
>
On Fri, 17 Jun 2016 15:32:20 +0200 Vlastimil Babka wrote:
> On 06/17/2016 09:57 AM, js1...@gmail.com wrote:
> > From: Sudip Mukherjee
> >
> > We have dereferenced page_ext before checking it. Lets check it first
> > and then used it.
> >
> > Link:
> >
> >> Also what's the content of your /etc/kdump.conf file?
> >>
> >
> > #raw /dev/sda5
> > #ext4 /dev/sda3
> > #ext4 LABEL=/boot
> > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > #net my.server.com:/export/tmp
> > #net u...@my.server.com
> > path /var/crash
> > #ext4 /dev/nvme0n1
> >
> >> Also what's the content of your /etc/kdump.conf file?
> >>
> >
> > #raw /dev/sda5
> > #ext4 /dev/sda3
> > #ext4 LABEL=/boot
> > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > #net my.server.com:/export/tmp
> > #net u...@my.server.com
> > path /var/crash
> > #ext4 /dev/nvme0n1
> >
On Fri, Jun 24, 2016 at 12:30:56PM -0500, Andrew F. Davis wrote:
> On 06/24/2016 11:46 AM, Guenter Roeck wrote:
> > On Fri, Jun 24, 2016 at 10:02:51AM -0500, Andrew F. Davis wrote:
> >> On 06/18/2016 10:16 AM, Guenter Roeck wrote:
> >>>
> >>> The chip registers are 16 bit. Can you repeat the
On Fri, Jun 24, 2016 at 12:30:56PM -0500, Andrew F. Davis wrote:
> On 06/24/2016 11:46 AM, Guenter Roeck wrote:
> > On Fri, Jun 24, 2016 at 10:02:51AM -0500, Andrew F. Davis wrote:
> >> On 06/18/2016 10:16 AM, Guenter Roeck wrote:
> >>>
> >>> The chip registers are 16 bit. Can you repeat the
On Fri, Jun 24, 2016 at 07:13:25PM +0100, Mel Gorman wrote:
> On Fri, Jun 24, 2016 at 09:46:18AM -0700, Guenter Roeck wrote:
> > > Ok, is there any chance you could test the mm-vmscan-node-lru-v8r12
> > > branch from git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> > > please?
> > >
On Fri, Jun 24, 2016 at 07:13:25PM +0100, Mel Gorman wrote:
> On Fri, Jun 24, 2016 at 09:46:18AM -0700, Guenter Roeck wrote:
> > > Ok, is there any chance you could test the mm-vmscan-node-lru-v8r12
> > > branch from git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> > > please?
> > >
On Fri, Jun 24, 2016 at 1:05 PM, Casey Schaufler wrote:
> On 6/24/2016 12:11 PM, Paul Moore wrote:
>> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
>> wrote:
>>> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>>>
>>> Back in
On Fri, Jun 24, 2016 at 1:05 PM, Casey Schaufler wrote:
> On 6/24/2016 12:11 PM, Paul Moore wrote:
>> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
>> wrote:
>>> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>>>
>>> Back in 2007 I made what turned out to be a rather serious
On Fri, Jun 24, 2016 at 8:18 AM, Casey Schaufler wrote:
> On 6/24/2016 1:40 AM, Michael Kerrisk (man-pages) wrote:
>> So, I just want to check my understanding of a couple of points:
>>
>> 1. The commoncap LSM is invoked first, and if it denies access,
>>then no
On Fri, Jun 24, 2016 at 8:18 AM, Casey Schaufler wrote:
> On 6/24/2016 1:40 AM, Michael Kerrisk (man-pages) wrote:
>> So, I just want to check my understanding of a couple of points:
>>
>> 1. The commoncap LSM is invoked first, and if it denies access,
>>then no further LSM is/needs to be
On 6/24/2016 12:11 PM, Paul Moore wrote:
> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
> wrote:
>> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>>
>> Back in 2007 I made what turned out to be a rather serious
>> mistake in the implementation of the
On 6/24/2016 12:11 PM, Paul Moore wrote:
> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
> wrote:
>> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>>
>> Back in 2007 I made what turned out to be a rather serious
>> mistake in the implementation of the Smack security module.
On Fri, Jun 24 2016 at 3:58pm -0400,
kbuild test robot <l...@intel.com> wrote:
> Hi,
>
> [auto build test WARNING on dm/for-next]
> [also build test WARNING on v4.7-rc4 next-20160624]
> [if your patch is applied to the wrong git tree, please drop us a note to
>
On Fri, Jun 24 2016 at 3:58pm -0400,
kbuild test robot wrote:
> Hi,
>
> [auto build test WARNING on dm/for-next]
> [also build test WARNING on v4.7-rc4 next-20160624]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
Hi,
[auto build test ERROR on dm/for-next]
[also build test ERROR on v4.7-rc4 next-20160624]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Toshi-Kani/dm-stripe-add-DAX-support/20160625-022600
Hi,
[auto build test ERROR on dm/for-next]
[also build test ERROR on v4.7-rc4 next-20160624]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Toshi-Kani/dm-stripe-add-DAX-support/20160625-022600
Hi,
[auto build test WARNING on dm/for-next]
[also build test WARNING on v4.7-rc4 next-20160624]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Toshi-Kani/dm-stripe-add-DAX-support/20160625
Hi,
[auto build test WARNING on dm/for-next]
[also build test WARNING on v4.7-rc4 next-20160624]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Toshi-Kani/dm-stripe-add-DAX-support/20160625
Am Dienstag, 21. Juni 2016, 18:30:05 schrieb Frank Wang:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank Wang
Hello,
thank you for the review.
On 24.6.2016 04:41, Chen-Yu Tsai wrote:
> On Fri, Jun 24, 2016 at 3:20 AM, wrote:
>> From: Josef Gajdusek
>>
>> Add a node describing the Security ID memory to the Allwinner H3 .dtsi file.
>>
>> Signed-off-by: Josef Gajdusek
Am Dienstag, 21. Juni 2016, 18:30:05 schrieb Frank Wang:
> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> than rk3288 and before, and most of phy-related registers are also
> different from the past, so a new phy driver is required necessarily.
>
> Signed-off-by: Frank Wang
Hello,
thank you for the review.
On 24.6.2016 04:41, Chen-Yu Tsai wrote:
> On Fri, Jun 24, 2016 at 3:20 AM, wrote:
>> From: Josef Gajdusek
>>
>> Add a node describing the Security ID memory to the Allwinner H3 .dtsi file.
>>
>> Signed-off-by: Josef Gajdusek
>> ---
>>
On 6/24/2016 12:15 PM, Paul Moore wrote:
> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
> wrote:
>> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs
>>
>> The /proc/.../attr/current interface is used by all three
>> Linux security modules (SELinux,
On 6/24/2016 12:15 PM, Paul Moore wrote:
> On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler
> wrote:
>> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs
>>
>> The /proc/.../attr/current interface is used by all three
>> Linux security modules (SELinux, Smack and AppArmor) to
>>
This patch adds a new prune_icache_sb function for the VFS slab
shrinker to call. Trying to directly free the inodes from memory
might deadlock because it evicts inodes, which calls into DLM
to acquire the glock. The DLM, in turn, may block on a pending
fence operation, which may already be
This patch adds a new prune_icache_sb function for the VFS slab
shrinker to call. Trying to directly free the inodes from memory
might deadlock because it evicts inodes, which calls into DLM
to acquire the glock. The DLM, in turn, may block on a pending
fence operation, which may already be
Hi William,
Am Dienstag, 21. Juni 2016, 17:11:44 schrieb William Wu:
> On 06/20/2016 10:44 PM, Heiko Stübner wrote:
> > Am Freitag, 17. Juni 2016, 17:18:59 schrieb William Wu:
> >> On 06/17/2016 07:15 AM, Heiko Stübner wrote:
> >>> Am Donnerstag, 2. Juni 2016, 20:34:56 schrieb William Wu:
>
In July 2011, near patch b0d40c92adafde7c2d81203ce7c1c69275f41140,
Dave Chinner introduced the concept of per-superblock shrinkers.
However, vfs still uses its own function, prune_icache_sb, which
gives almost no control to the underlying file system over the
inode eviction.
The trouble is, some
Hi William,
Am Dienstag, 21. Juni 2016, 17:11:44 schrieb William Wu:
> On 06/20/2016 10:44 PM, Heiko Stübner wrote:
> > Am Freitag, 17. Juni 2016, 17:18:59 schrieb William Wu:
> >> On 06/17/2016 07:15 AM, Heiko Stübner wrote:
> >>> Am Donnerstag, 2. Juni 2016, 20:34:56 schrieb William Wu:
>
In July 2011, near patch b0d40c92adafde7c2d81203ce7c1c69275f41140,
Dave Chinner introduced the concept of per-superblock shrinkers.
However, vfs still uses its own function, prune_icache_sb, which
gives almost no control to the underlying file system over the
inode eviction.
The trouble is, some
This patch adds filesystem-specific callbacks for shrinking the
inode cache, prune_icache_sb. This is provided for filesystems in
which the default VFS prune_icache_sb needs to be delayed due to
filesystem locking requirements not met by vfs.
Signed-off-by: Bob Peterson
---
This patch adds filesystem-specific callbacks for shrinking the
inode cache, prune_icache_sb. This is provided for filesystems in
which the default VFS prune_icache_sb needs to be delayed due to
filesystem locking requirements not met by vfs.
Signed-off-by: Bob Peterson
---
On Fri, Jun 24, 2016 at 02:43:00PM -0400, Stefan Berger wrote:
> On 06/24/2016 01:48 PM, Jason Gunthorpe wrote:
> >On Fri, Jun 24, 2016 at 10:36:55AM -0400, Stefan Berger wrote:
> >>Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
> >>instance from having the typical sysfs
On Fri, Jun 24, 2016 at 02:43:00PM -0400, Stefan Berger wrote:
> On 06/24/2016 01:48 PM, Jason Gunthorpe wrote:
> >On Fri, Jun 24, 2016 at 10:36:55AM -0400, Stefan Berger wrote:
> >>Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
> >>instance from having the typical sysfs
From: Qiang Zhao
Date: Fri, 24 Jun 2016 02:00:33 +
> On Thu, 2016-06-23 at 10:59PM, David Miller wrote:
>> -Original Message-
>> From: David Miller [mailto:da...@davemloft.net]
>> Sent: Thursday, June 23, 2016 10:59 PM
>> To: Qiang Zhao
>> Cc:
Enable configuration options useful for the Vybrid Tower platform:
- CRTouch Touchscreen support.
- DRM support for Freescale DCU.
Regenerated config using savedefconfig (which removes some configs
which are now enabled by default).
Signed-off-by: Anthony Felice
---
This adds a node for crtouch, the touchscreen controller of the Vybrid
Tower. Pinmux for the gpio irq used by crtouch is also defined in this
commit.
Signed-off-by: Anthony Felice
---
arch/arm/boot/dts/vf610-twr.dts | 14 ++
1 file changed, 14 insertions(+)
From: Qiang Zhao
Date: Fri, 24 Jun 2016 02:00:33 +
> On Thu, 2016-06-23 at 10:59PM, David Miller wrote:
>> -Original Message-
>> From: David Miller [mailto:da...@davemloft.net]
>> Sent: Thursday, June 23, 2016 10:59 PM
>> To: Qiang Zhao
>> Cc: o...@buserror.net;
Enable configuration options useful for the Vybrid Tower platform:
- CRTouch Touchscreen support.
- DRM support for Freescale DCU.
Regenerated config using savedefconfig (which removes some configs
which are now enabled by default).
Signed-off-by: Anthony Felice
---
This adds a node for crtouch, the touchscreen controller of the Vybrid
Tower. Pinmux for the gpio irq used by crtouch is also defined in this
commit.
Signed-off-by: Anthony Felice
---
arch/arm/boot/dts/vf610-twr.dts | 14 ++
1 file changed, 14 insertions(+)
diff --git
Add driver for the Vybrid Tower CRTouch-based touchscreen. This is
required for the touchscreen on the TWR-LCD-RGB to work on the Vybrid
Tower platform.
There is a known issue with this driver: rarely, SW1 on the TWR-LCD-RGB
module needs to be pressed in order for the touchscreen to begin
This adds nodes to enable tcon0 and dcu0 for the Vybrid Tower. These
are used to drive the Vybrid Tower TWR-LCD-RGB display. Also, a node
for the nec nl4827hc19-05b panel on the TWR-LCD-RGB display has been
added.
Signed-off-by: Anthony Felice
---
This patchset enables the TWR-LCD-RGB display and the CRTouch-based touchscreen
on the Vybrid Tower platform. Both display and touchscreen have been tested and
verified working with this patchset on a Rev J Vybrid Tower system.
Anthony Felice (4):
ARM: dts: vf610-twr: Enable display controller
Add driver for the Vybrid Tower CRTouch-based touchscreen. This is
required for the touchscreen on the TWR-LCD-RGB to work on the Vybrid
Tower platform.
There is a known issue with this driver: rarely, SW1 on the TWR-LCD-RGB
module needs to be pressed in order for the touchscreen to begin
This adds nodes to enable tcon0 and dcu0 for the Vybrid Tower. These
are used to drive the Vybrid Tower TWR-LCD-RGB display. Also, a node
for the nec nl4827hc19-05b panel on the TWR-LCD-RGB display has been
added.
Signed-off-by: Anthony Felice
---
arch/arm/boot/dts/vf610-twr.dts | 48
This patchset enables the TWR-LCD-RGB display and the CRTouch-based touchscreen
on the Vybrid Tower platform. Both display and touchscreen have been tested and
verified working with this patchset on a Rev J Vybrid Tower system.
Anthony Felice (4):
ARM: dts: vf610-twr: Enable display controller
Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I:
> Hi,
>
> On Thursday 23 June 2016 06:21 PM, Chris Zhong wrote:
> > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB
> > Type-C PHY is designed to support the USB3 and DP applications. The
> > PHY basically has
Am Donnerstag, 23. Juni 2016, 18:27:52 schrieb Kishon Vijay Abraham I:
> Hi,
>
> On Thursday 23 June 2016 06:21 PM, Chris Zhong wrote:
> > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB
> > Type-C PHY is designed to support the USB3 and DP applications. The
> > PHY basically has
On Fri, 24 Jun 2016, KY Srinivasan wrote:
How so? Can you expand on the racy part. The subtraction is done on a local
copy of
the value.
Yeah, you're right. I took a look at the generated code and I was unnecessarily
worried
about the window between the return value and the subtraction.
On Fri, 24 Jun 2016, KY Srinivasan wrote:
How so? Can you expand on the racy part. The subtraction is done on a local
copy of
the value.
Yeah, you're right. I took a look at the generated code and I was unnecessarily
worried
about the window between the return value and the subtraction.
The tip gcc includes an optimization mode that converts
64-bit divides into 128-bit multiplies using __multi3.
Export the symbol so that modules can find it. We just
export unconditionally without worrying about the gcc
version, since the symbol has been in libgcc forever and
the function is less
The tip gcc includes an optimization mode that converts
64-bit divides into 128-bit multiplies using __multi3.
Export the symbol so that modules can find it. We just
export unconditionally without worrying about the gcc
version, since the symbol has been in libgcc forever and
the function is less
On Fri, Jun 17, 2016 at 11:10:43PM +0200, Jarkko Sakkinen wrote:
> extern int tpm_get_timeouts(struct tpm_chip *);
> -extern void tpm_gen_interrupt(struct tpm_chip *);
> +void tpm_gen_interrupt(struct tpm_chip *);
Dropping the argument name is not the kernel standard, if these lines
are going to
On Fri, Jun 17, 2016 at 11:10:43PM +0200, Jarkko Sakkinen wrote:
> extern int tpm_get_timeouts(struct tpm_chip *);
> -extern void tpm_gen_interrupt(struct tpm_chip *);
> +void tpm_gen_interrupt(struct tpm_chip *);
Dropping the argument name is not the kernel standard, if these lines
are going to
There was only one use of __initdata_refok and __exit_refok
__init_refok was used 46 times against 82 for __ref.
Those definitions are obsolete since
commit 312b1485fb50
("Introduce new section reference annotations tags: __ref,
__refdata, __refconst")
This patch removes the following
There was only one use of __initdata_refok and __exit_refok
__init_refok was used 46 times against 82 for __ref.
Those definitions are obsolete since
commit 312b1485fb50
("Introduce new section reference annotations tags: __ref,
__refdata, __refconst")
This patch removes the following
On Thu, Jun 23, 2016 at 08:51:03PM +0800, Chris Zhong wrote:
> This patch adds a binding that describes the cdn DP controller for
> rk3399.
>
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v3:
> - add SoC specific compatible string
> - remove reg = <1>;
>
> Changes
On Thu, Jun 23, 2016 at 08:51:03PM +0800, Chris Zhong wrote:
> This patch adds a binding that describes the cdn DP controller for
> rk3399.
>
> Signed-off-by: Chris Zhong
>
> ---
>
> Changes in v3:
> - add SoC specific compatible string
> - remove reg = <1>;
>
> Changes in v2: None
> Changes
On Thu, Jun 23, 2016 at 08:51:01PM +0800, Chris Zhong wrote:
> This patch adds a binding that describes the Rockchip USB Type-C PHY
> for rk3399
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Tomasz Figa
> Reviewed-by: Kever Yang
On Thu, Jun 23, 2016 at 08:51:01PM +0800, Chris Zhong wrote:
> This patch adds a binding that describes the Rockchip USB Type-C PHY
> for rk3399
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Tomasz Figa
> Reviewed-by: Kever Yang
>
> ---
>
> Changes in v3:
> - use compatible:
On Fri, Jun 24, 2016 at 09:46:05AM -0700, James Bottomley wrote:
> On Mon, 2016-06-20 at 13:05 -0700, Davidlohr Bueso wrote:
> > Hi,
> >
> > The series is really straightforward and based on Peter's work that
> > introduces[1] the atomic_fetch_$op machinery. Only patch 1 implements
> > the actual
On Fri, Jun 24, 2016 at 09:46:05AM -0700, James Bottomley wrote:
> On Mon, 2016-06-20 at 13:05 -0700, Davidlohr Bueso wrote:
> > Hi,
> >
> > The series is really straightforward and based on Peter's work that
> > introduces[1] the atomic_fetch_$op machinery. Only patch 1 implements
> > the actual
On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs
>
> The /proc/.../attr/current interface is used by all three
> Linux security modules (SELinux, Smack and AppArmor) to
> report and modify the
On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs
>
> The /proc/.../attr/current interface is used by all three
> Linux security modules (SELinux, Smack and AppArmor) to
> report and modify the process security attribute.
On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>
> Back in 2007 I made what turned out to be a rather serious
> mistake in the implementation of the Smack security module.
> The SELinux module used
The inline cpu_pm_register_notifier stub simply allows compilation
on systems with CONFIG_CPU_PM disabled. The dummy
cpu_pm_register_notifier does not register an trap_pm_init,
r4k_tlb_init_pm and r4k_cache_init_pm at all.The inline
cpu_pm_register_notifier should return to indicate lack of
On Thu, Jun 23, 2016 at 5:11 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 2/3] LSM: module hierarchy in /proc/.../attr
>
> Back in 2007 I made what turned out to be a rather serious
> mistake in the implementation of the Smack security module.
> The SELinux module used an interface in /proc to
The inline cpu_pm_register_notifier stub simply allows compilation
on systems with CONFIG_CPU_PM disabled. The dummy
cpu_pm_register_notifier does not register an trap_pm_init,
r4k_tlb_init_pm and r4k_cache_init_pm at all.The inline
cpu_pm_register_notifier should return to indicate lack of
On Fri, Jun 24, 2016 at 9:02 AM, Jason Cooper wrote:
> Thomas,
>
> Sorry for wandering off the topic of your series. The big take away for
> me is that you and Kees are concerned about x86 systems pre-RDRAND.
> Just as I'm concerned about deployed embedded systems without
On Fri, Jun 24, 2016 at 9:02 AM, Jason Cooper wrote:
> Thomas,
>
> Sorry for wandering off the topic of your series. The big take away for
> me is that you and Kees are concerned about x86 systems pre-RDRAND.
> Just as I'm concerned about deployed embedded systems without bootloader
> support
On Thu, Jun 23, 2016 at 5:10 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 1/3] LSM: Add /sys/kernel/security/lsm
>
> I got tired of having to find indirect ways to
> determine what security modules are active on a system.
> I have added /sys/kernel/security/lsm, which
On Thu, Jun 23, 2016 at 5:10 PM, Casey Schaufler wrote:
> Subject: [PATCH v4 1/3] LSM: Add /sys/kernel/security/lsm
>
> I got tired of having to find indirect ways to
> determine what security modules are active on a system.
> I have added /sys/kernel/security/lsm, which contains a
> comma
On Fri, Jun 24, 2016 at 12:41 PM, Rob Herring wrote:
> On Tue, Jun 21, 2016 at 11:25:49PM -0300, Bruno Herrera wrote:
>> Signed-off-by: Bruno Herrera
>> ---
>> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
>> 1 file changed, 1 insertion(+)
>>
>>
On Fri, Jun 24, 2016 at 12:41 PM, Rob Herring wrote:
> On Tue, Jun 21, 2016 at 11:25:49PM -0300, Bruno Herrera wrote:
>> Signed-off-by: Bruno Herrera
>> ---
>> Documentation/devicetree/bindings/usb/dwc2.txt | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git
On Fri, Jun 24, 2016 at 09:34:30AM -0700, Davidlohr Bueso wrote:
> On Thu, 23 Jun 2016, Peter Zijlstra wrote:
>
> >-
> >/* atomic_fetch_inc_relaxed */
> >#ifndef atomic_fetch_inc_relaxed
> >+
> >+#ifndef atomic_fetch_inc
>
> #define atomic_fetch_inc(v) (atomic_fetch_add(1, v))
Ah yes.
>
On Fri, Jun 24, 2016 at 09:34:30AM -0700, Davidlohr Bueso wrote:
> On Thu, 23 Jun 2016, Peter Zijlstra wrote:
>
> >-
> >/* atomic_fetch_inc_relaxed */
> >#ifndef atomic_fetch_inc_relaxed
> >+
> >+#ifndef atomic_fetch_inc
>
> #define atomic_fetch_inc(v) (atomic_fetch_add(1, v))
Ah yes.
>
On 06/24/2016 01:48 PM, Jason Gunthorpe wrote:
On Fri, Jun 24, 2016 at 10:36:55AM -0400, Stefan Berger wrote:
Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
instance from having the typical sysfs entries that shows the state of the
TPM. The flag is to be set in the
On 06/24/2016 01:48 PM, Jason Gunthorpe wrote:
On Fri, Jun 24, 2016 at 10:36:55AM -0400, Stefan Berger wrote:
Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
instance from having the typical sysfs entries that shows the state of the
TPM. The flag is to be set in the
On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> On Fri, Jun 24 2016 at 2:23pm -0400,
> Toshi Kani wrote:
:
> Thanks, once jens queues the block changes I'll be able to pull this in
> to linux-dm.git
>
> BTW, if in your testing you could evaluate/quantify any extra
On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> On Fri, Jun 24 2016 at 2:23pm -0400,
> Toshi Kani wrote:
:
> Thanks, once jens queues the block changes I'll be able to pull this in
> to linux-dm.git
>
> BTW, if in your testing you could evaluate/quantify any extra overhead
> from DM
Hi Tim,
On 06/24/16 04:19, Tim Wang wrote:
> There is one condition that need cat the dtb files
> into one dtb.img which can support several boards
> use same SoC platform.
>
> And the original dtb file size is not aligned to any base.
> This may cause "Synchronous Abort" when load from a
Hi Tim,
On 06/24/16 04:19, Tim Wang wrote:
> There is one condition that need cat the dtb files
> into one dtb.img which can support several boards
> use same SoC platform.
>
> And the original dtb file size is not aligned to any base.
> This may cause "Synchronous Abort" when load from a
On Fri, Jun 24, 2016 at 07:58:32PM +0300, Grygorii Strashko wrote:
> Oh. nice :( So, seems, I'd need to send v3. Right?
> By the way, this code hasn't been introduced by this patch - I've
> just moved whole function from one place to another.
Well since it is moving I would think that was a handy
On Fri, Jun 24, 2016 at 07:58:32PM +0300, Grygorii Strashko wrote:
> Oh. nice :( So, seems, I'd need to send v3. Right?
> By the way, this code hasn't been introduced by this patch - I've
> just moved whole function from one place to another.
Well since it is moving I would think that was a handy
On Fri, Jun 24, 2016 at 10:56 AM, Linus Torvalds
wrote:
> On Fri, Jun 24, 2016 at 10:47 AM, Andy Lutomirski wrote:
>>
>> FWIW, your patch is much more lenient than my approach.
>
> I hate big flag-days - they cause so much pain for everybody.
On Fri, Jun 24, 2016 at 10:56 AM, Linus Torvalds
wrote:
> On Fri, Jun 24, 2016 at 10:47 AM, Andy Lutomirski wrote:
>>
>> FWIW, your patch is much more lenient than my approach.
>
> I hate big flag-days - they cause so much pain for everybody. The
> people who get it to work and can test it,
301 - 400 of 1424 matches
Mail list logo