When we leave the delete interface function, there are still netdev
hooks that might try to process the device. We're short-circuiting some
of that by changing the interface type and clearing ieee80211_ptr. This
means we skip NETDEV_UNREGISTER_FINAL in cfg80211. Fortunately, that is
currently a no-
Signed-off-by: Brian Norris
---
drivers/net/wireless/marvell/mwifiex/cfp.c | 4 +---
drivers/net/wireless/marvell/mwifiex/sta_cmd.c | 8 ++--
drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c | 5 ++---
3 files changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/net/w
It's always called with 'true' -- we only determine it 'false' locally
within this function. So drop the parameter.
Also, this should be 'bool' (since we use true/false), not 'u32'.
Signed-off-by: Brian Norris
---
drivers/net/wireless/marvell/mwifiex/cmdevt.c | 5 +++--
drivers/net/wireless/mar
This keeps annoying me.
Signed-off-by: Brian Norris
---
drivers/net/wireless/marvell/mwifiex/pcie.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/marvell/mwifiex/pcie.c
b/drivers/net/wireless/marvell/mwifiex/pcie.c
index c86119b05f52..4f1d946ea460 1006
The .idle_time field *should* be unused, but technically, we're allowing
unitialized stack garbage to pass all the way through to the firmware
host command. Let's zero it out instead.
Signed-off-by: Brian Norris
---
drivers/net/wireless/marvell/mwifiex/sta_ioctl.c | 6 +++---
1 file changed, 3 i
free_irq() already calls synchronize_irq() in a non-racy manner. Calling
synchronize_irq() here is redundant.
Signed-off-by: Brian Norris
---
drivers/net/wireless/marvell/mwifiex/pcie.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/wireless/marvell/mwifiex/pcie.c
b/drivers/n
When PCIe FLR code was added, it explicitly copy-and-pasted much of
mwifiex_remove_card() into mwifiex_shutdown_sw(). This is unnecessary,
as almost all of the code should be reused.
Let's reunite what we can for now.
The only functional changes for now:
* call netif_device_detach() in the remo
Hi Alex,
[auto build test WARNING on next-20170522]
[also build test WARNING on v4.12-rc2]
[cannot apply to v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/Alex-Naidis
In rogue cases (due to other bugs) it's possible we try to process an
old command response *after* resetting the device. This could trigger a
double-free (or the SKB can get reallocated elsewhere...causing other
memory corruptions) in mwifiex_pcie_process_cmd_complete().
For safety (and symmetry)
On Wed, May 24, 2017 at 03:22:11PM -0700, Jarkko Sakkinen wrote:
> On Wed, May 24, 2017 at 05:39:41PM -0400, Stefan Berger wrote:
> > To prevent userspace from sending the TPM driver command to set
> > the locality, we need to check every command that is sent from
> > user space. To distinguish use
On Wed, May 24, 2017 at 07:03:27PM -0400, Stefan Berger wrote:
> On 05/24/2017 06:21 PM, Jarkko Sakkinen wrote:
> > On Wed, May 24, 2017 at 05:39:40PM -0400, Stefan Berger wrote:
> > > Implement the request_locality function. To set the locality on the
> > > backend we define vendor-specific TPM 1.
I'm not a kernel expert so maybe I don't understand this right, but...
I think this might have been done this way to ensure that the driver
can get initialized correctly regardless of probe ordering.
coreboot_table_find() may fail with -EPROBE_DEFER if the
coreboot_table driver and its dependent (c
Enable queued rwlocks for SPARC. Here are the discussions on this feature
when this was introduced.
https://lwn.net/Articles/572765/
https://lwn.net/Articles/582200/
Cleaned-up the arch_read_xxx and arch_write_xxx definitions in spinlock_64.h.
These routines are replaced by the functions in includ
This patch makes the necessary changes in SPARC architecture to enable
queued spinlock support. Here are some of the earlier discussions about
this feature.
https://lwn.net/Articles/561775/
https://lwn.net/Articles/590243/
Cleaned-up the spinlock_64.h. The definitions of arch_spin_xxx are
replaced
This series of patches enables queued rwlock and queued spinlock support
for SPARC. These features were introduced some time ago in upstream.
Here are some of the earlier discussions.
https://lwn.net/Articles/572765/
https://lwn.net/Articles/582200/
https://lwn.net/Articles/561775/
https://lwn.net/
Found this problem while enabling queued rwlock on SPARC.
The parameter CONFIG_CPU_BIG_ENDIAN is used to clear the
specific byte in qrwlock structure. Without this parameter,
we clear the wrong byte. Here is the code.
static inline u8 *__qrwlock_write_byte(struct qrwlock *lock)
{
return (
Saw these compile errors on SPARC when queued rwlock feature is enabled.
CC kernel/locking/qrwlock.o
kernel/locking/qrwlock.c: In function ‘queued_read_lock_slowpath’:
kernel/locking/qrwlock.c:89: error: implicit declaration of function
‘arch_spin_lock’
kernel/locking/qrwlock.c:102: error:
SPARC supports 32 bit and 64 bit xchg right now. Add the support
for 16 bit (2 byte) xchg. This is required to support queued spinlock
feature which uses 2 byte xchg. This is achieved using 4 byte cas
instructions with byte manipulations.
Also re-arranged the code to call __cmpxchg_u32 inside xchg
Saw these compile errors on SPARC when queued rwlock feature is enabled.
CC kernel/locking/qrwlock.o
In file included from ./include/asm-generic/qrwlock_types.h:5,
from ./arch/sparc/include/asm/qrwlock.h:4,
from kernel/locking/qrwlock.c:24:
./arch/sparc/
On 05/24/2017 06:19 AM, Michael Ellerman wrote:
> Michael Bringmann writes:
>
>> On 05/23/2017 04:49 PM, Reza Arbab wrote:
>>> On Tue, May 23, 2017 at 03:05:08PM -0500, Michael Bringmann wrote:
On 05/23/2017 10:52 AM, Reza Arbab wrote:
> On Tue, May 23, 2017 at 10:15:44AM -0500, Michae
SPARC supports 32 bit and 64 bit cmpxchg right now. Add support
for 8 bit (1 byte) cmpxchg. This is required to support queued
rwlocks feature which uses 1 byte cmpxchg.
The function __cmpxchg_u8 here uses the 4 byte cas instruction with a
byte manipulation to achieve 1 byte cmpxchg.
Signed-off-
Hi Ian,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.12-rc2 next-20170524]
[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/Ian-Abbott/bug-fix-problem-including-linux-bug
On 05/25/2017 01:35 AM, David Daney wrote:
Some JITs can optimize comparisons with zero. Add a couple of
BPF_JSGE tests against immediate zero.
Signed-off-by: David Daney
Thanks for the tests!
Acked-by: Daniel Borkmann
This is quite a big update because it includes a rework of the lpfc
driver to separate the NVMe part from the FC part. The reason for
doing this is because two separate trees (the nvme and scsi trees
respectively) want to update the individual components and this
separation will prevent a really n
erasesize is meaningful for flash devices but for SRAM there is no
concept of an erase block so erasesize is set to 0. When partitioning
these devices instead of ensuring partitions fall on erasesize
boundaries we ensure they fall on writesize boundaries.
Helped-by: Boris Brezillon
Signed-off-by:
The mchp23lcv1024 is similar to the mchp23k256, the differences (from a
software point of view) are the capacity of the chip and the size of the
addresses used.
There is no way to detect the specific chip so we must be told via a
Device Tree or default to mchp23k256 when device tree is not used.
Setting the of_node for the mtd device allows the generic mtd code to
setup the partitions. Additionally we must specify a non-zero erasesize
for the partitions to be writeable.
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
Tested-by: Andrew Lunn
---
Changes in v2
- collect revew/test f
Use mtd_device_register() instead of mtd_device_parse_register() to
eliminate two unused parameters.
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
Tested-by: Andrew Lunn
---
Changes in v2
- collect review/test from Andrew
Changes in v3:
- None
Changes in v4:
- None
drivers/mtd/devices
This series adds device tree support to the mchp23k256 driver and
support for the mchp23lcv1024 chip. I suspect there are more compatible
variants that we could now enumerate if desired.
Chris Packham (5):
mtd: mchp23k256: Add OF device ID table
mtd: mchp23k256: switch to mtd_device_register()
This allows registering of this device via a Device Tree.
Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
Tested-by: Andrew Lunn
---
Changes in v2:
- collect review/test from Andrew
Changes in v3:
- None
Changes in v4:
- None
.../devicetree/bindings/mtd/microchip,mchp23k256.txt | 18 +
I will get a log based on the latest 4.12 kernel to show what happens
one way or the other, with this patch removed.
On 05/24/2017 09:36 AM, Reza Arbab wrote:
> On Tue, May 23, 2017 at 05:44:23PM -0500, Michael Bringmann wrote:
>> On 05/23/2017 04:49 PM, Reza Arbab wrote:
>>> On Tue, May 23, 2017
On 05/09/2017 09:17 AM, Tejun Heo wrote:
Currently, rq->leaf_cfs_rq_list is a traversal ordered list of all
live cfs_rqs which have ever been active on the CPU; unfortunately,
this makes update_blocked_averages() O(total number of CPU cgroups)
which isn't scalable at all.
The next patch will m
On 05/23/2017 03:10 PM, Tejun Heo wrote:
> Hello,
>
> On Tue, May 23, 2017 at 03:09:07PM -0500, Michael Bringmann wrote:
>> To confirm, you want the WARN_ON(cpumask_any(pool->attrs->cpumask) >=
>> NR_CPUS)
>> at the point where I place my current patch?
>
> Yeah, cpumask_weight() probably is a
Some JITs can optimize comparisons with zero. Add a couple of
BPF_JSGE tests against immediate zero.
Signed-off-by: David Daney
---
lib/test_bpf.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/lib/test_bpf.c b/lib/test_bpf.c
index 889bc31..be88cba 1
Hi Mark
Cc: DRM maintainer
> > ALSA SoC needs to know connected DAI ID for probing.
> > It is not a big problem if device/driver was only for sound,
> > but getting DAI ID will be difficult if device includes both
> > Video/Sound, like HDMI.
>
> As far as I understand what's going on with the gr
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/phy/marvell.c
between commit:
f2899788353c ("net: phy: marvell: Limit errata to 88m1101")
from the net tree and commit:
0c3439bc7773 ("net: phy: Marvell: checkpatch - Comments")
from the net-next tree.
Hi,
On Wed, May 24, 2017 at 2:32 PM, Andrew Morton
wrote:
> On Wed, 24 May 2017 14:22:29 -0700 Matthias Kaehlcke
> wrote:
>
>> I'm not a kernel maintainer, so it's not my decision whether this
>> warning should be silenced, my personal opinion is that it's benfits
>> outweigh the inconveniences
On Wed, May 24, 2017 at 08:03:14PM +0530, srishti sharma wrote:
This driver is not in Greg KH's staging tree. You may like to work off
of that tree when doing staging patches.
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
To aid you future patches here are a couple of minor
Hi Ian,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.12-rc2 next-20170524]
[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/Ian-Abbott/bug-fix-problem-including-linux
This patch fixes the miscoded use of return value of snprintf
by using the scnprintf function which returns the length of actual
string created in the buffer.
Signed-off-by: Harinath Nampally
---
drivers/staging/iio/light/tsl2x7x.c | 20 ++--
1 file changed, 10 insertions(+), 10
before freeing again.
>
> I applied this patch, and it appears to fix the bug for me.
>
> Signed-off-by: Steven Rostedt (VMware)
Awesome, this also cures my panic:
mcgrof@piggy ~/linux-next (git::20170524-fixwarn)$ sudo
tools/testing/selftests/ftrace/ftracetest
...
# of passed: 45
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
So the combination of both:
Tested-by: Luis R. Rodriguez
Luis
We poke at proc sysctl enough that really we should declare it
maintained. We'll just be Cc'd and sending updates / ACK'ing
changes through akpm's tree.
Acked-by: Kees Cook
Signed-off-by: Luis R. Rodriguez
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAIN
On 2017-05-24 17:06, Ian Abbott wrote:
If "include/linux/kernel.h" includes , a circular
dependency is introduced when "include/asm-generic/bug.h" includes
. This results in build breakage when something
includes before for architectures that
select `CONFIG_GENERIC_BUG` because `struct bug_ent
On 05/24/2017 06:21 PM, Jarkko Sakkinen wrote:
On Wed, May 24, 2017 at 05:39:40PM -0400, Stefan Berger wrote:
Implement the request_locality function. To set the locality on the
backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
a command to the backend to set the locality for
On Wed, May 24, 2017 at 10:08 AM, Benjamin Tissoires
wrote:
> Hi Rafael,
>
> On May 15 2017 or thereabouts, Rafael J. Wysocki wrote:
>> >> >> Benjamin, my understanding is that this is the case, is it correct?
>> >> >
>> >> > That is correct. This patch I reverted introduces regression for
>> >>
On 05/24/2017 06:18 PM, Jarkko Sakkinen wrote:
On Wed, May 24, 2017 at 05:39:39PM -0400, Stefan Berger wrote:
Introduce the flag TPM_TRANSMIT_RAW that allows us to transmit
a command without recursing into the requesting of locality.
Signed-off-by: Stefan Berger
Reviewed-by: Jarkko Sakkinen
>>>>>> nand: No NAND device found
>>>>>> pxa3xx-nand f10d.flash: failed to scan nand at cs 0
>>>>>>
>>>>>> This was working around 4.11. I'll try to do some more digging tomorrow
>>>>>> to narro
From: Joshua Emele
The sky2_hw_down uses sky2_tx_complete to free pending frames stuck in
the HW queue. Because sky2_hw_down can be called from a process context,
the call to u64_stats_update_begin can result in deadlock.
Because the statistics do not require update as part of the sky2_hw_down
s
On Wed, May 24, 2017 at 3:00 PM, Andy Lutomirski wrote:
> On Wed, May 24, 2017 at 2:40 PM, Luis R. Rodriguez wrote:
>> From: Martin Fuzzey
>>
>> Commit 0cb64249ca500 ("firmware_loader: abort request if wait_for_completion
>> is interrupted") added via 4.0 added support to abort the fallback mech
at cs 0
> >>>>
> >>>> This was working around 4.11. I'll try to do some more digging tomorrow
> >>>> to narrow down a failure point but I thought I'd send this out now just
> >>>> in case it rings any bells.
> >>>>
&g
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git ms
head: 7daa984159c77d85f3ee053d5688ed7a47854613
commit: 7daa984159c77d85f3ee053d5688ed7a47854613 [7/7] mmap_sem: Use
percpu_rw_sema
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 201
On Wed, May 24, 2017 at 03:27:31PM -0700, Jarkko Sakkinen wrote:
> Removed struct tpm_pcrextend_in as it is not used for anything anymore.
>
> Signed-off-by: Jarkko Sakkinen
Another bit of code that I just push.
/Jarkko
> ---
> drivers/char/tpm/tpm.h | 6 --
> 1 file changed, 6 deletions(
Removed struct tpm_pcrextend_in as it is not used for anything anymore.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h
index dd1173427fb2..af05c1403c6e 100644
--- a/drivers/char/tp
On Wed, 24 May 2017 21:13:27 +0200 (CEST)
Thomas Gleixner wrote:
> > Oops: 0003 [#1] SMP
> > Modules linked in:
> > CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc2-test+ #42
> > Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6
> > 02/22/2014 task: 8802153a8000 task.stack: ff
On Wed, May 24, 2017 at 04:35:19AM -0700, Tahsin Erdogan wrote:
> ext4_xattr_block_set() calls dquot_alloc_block() to charge for an xattr
> block when new references are made. However if dquot_initialize() hasn't
> been called on an inode, request for charging is effectively ignored
> because ext4_
On Wed, May 24, 2017 at 05:39:41PM -0400, Stefan Berger wrote:
> To prevent userspace from sending the TPM driver command to set
> the locality, we need to check every command that is sent from
> user space. To distinguish user space commands from internally
> sent commands we introduce an addition
On Wed, May 24, 2017 at 05:39:40PM -0400, Stefan Berger wrote:
> Implement the request_locality function. To set the locality on the
> backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
> a command to the backend to set the locality for the next commands.
>
> To avoid recursing
On Wed, 24 May 2017, Punit Agrawal wrote:
On failing to migrate a page, soft_offline_huge_page() performs the
necessary update to the hugepage ref-count. When
!hugepage_migration_supported() , unmap_and_move_hugepage() also
decrements the page ref-count for the hugepage. The combined behaviour
l
On Wed, May 24, 2017 at 05:39:39PM -0400, Stefan Berger wrote:
> Introduce the flag TPM_TRANSMIT_RAW that allows us to transmit
> a command without recursing into the requesting of locality.
>
> Signed-off-by: Stefan Berger
> Reviewed-by: Jarkko Sakkinen
I'll rename the constant as TPM_TRANSMIT
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git ms
head: 7daa984159c77d85f3ee053d5688ed7a47854613
commit: 7daa984159c77d85f3ee053d5688ed7a47854613 [7/7] mmap_sem: Use
percpu_rw_sema
config: x86_64-acpi-redef+CONFIG_DEBUG_INFO_REDUCED (attached as .config)
compiler:
Hi David,
El Wed, May 24, 2017 at 01:36:21PM -0700 David Rientjes ha dit:
> On Tue, 23 May 2017, Matthias Kaehlcke wrote:
>
> > > diff --git a/include/linux/compiler-clang.h
> > > b/include/linux/compiler-clang.h
> > > index de179993e039..e1895ce6fa1b 100644
> > > --- a/include/linux/compiler-c
On 24/05/17 04:05 PM, Al Viro wrote:
>> I have designs to use these functions in scatterlist.c where they'd
>> almost certainly never be called on the um architecture but it does need
>> to compile.
>
> Then make it fail there.
Ok, will do. I'll send a v2 patch shortly.
> Incidentally, s390 ha
This should at least make vendors less nervous about Linux's APST
policy. I'm not aware of any concrete bugs it would fix (although I
was hoping it would fix the Samsung/Dell quirk).
Cc: sta...@vger.kernel.org # v4.11
Cc: Kai-Heng Feng
Cc: Mario Limonciello
Signed-off-by: Andy Lutomirski
---
This should fix all known regressions.
Andy Lutomirski (2):
nvme: Wait at least 6000ms before entering the deepest idle state
nvme: Quirk APST on Intel 600P/P3100 devices
drivers/nvme/host/core.c | 38 +++---
drivers/nvme/host/pci.c | 2 ++
2 files changed,
They have known firmware bugs. A fix is apparently in the works --
once fixed firmware is available, someone from Intel (Hi, Keith!)
can adjust the quirk accordingly.
Cc: sta...@vger.kernel.org # v4.11
Cc: Kai-Heng Feng
Cc: Mario Limonciello
Signed-off-by: Andy Lutomirski
---
drivers/nvme/hos
On Wed, May 24, 2017 at 04:00:52PM -0600, Logan Gunthorpe wrote:
> The user mode architecture does not provide ioremap or iounmap, and
> because of this, the arch won't build when the functions are used in some
> core libraries.
>
> I have designs to use these functions in scatterlist.c where they
#x27;d send this out now just
>>>> in case it rings any bells.
>>>>
>>>> The board I'm using (DB-88F6820-AMC) is unfortunately out-of tree but it
>>>> should be pretty close to the armada-388-db. I can make my dts available
>>>> if it&#x
Add a default ioremap function which was not provided in all
circumstances. (Only when CONFIG_PCI and CONFIG_TILEGX was set).
I have designs to use them in scatterlist.c where they'd likely never
be called with this architecture, but it is needed to compile.
Signed-off-by: Logan Gunthorpe
Signed
The user mode architecture does not provide ioremap or iounmap, and
because of this, the arch won't build when the functions are used in some
core libraries.
I have designs to use these functions in scatterlist.c where they'd
almost certainly never be called on the um architecture but it does need
On Wed, May 24, 2017 at 2:40 PM, Luis R. Rodriguez wrote:
> From: Martin Fuzzey
>
> Commit 0cb64249ca500 ("firmware_loader: abort request if wait_for_completion
> is interrupted") added via 4.0 added support to abort the fallback mechanism
> when a signal was detected and wait_for_completion_inte
This is a layering violation so we replace the uses with calls to
sg_page(). This is a prep patch for replacing page_link and this
is one of the very few uses outside of scatterlist.h.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
Cc: Stefani Seibold
Cc: Greg KH
Cc: Andrew Morton
This is a layering violation so we replace it with calls to
sg_page. This is a prep patch for replacing page_link and this
is one of the very few uses outside of scatterlist.h.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
Cc: Greg Kroah-Hartman
Cc: Gilad Ben-Yossef
---
drivers/
Two dma engine drivers directly accesses page_link assuming knowledge
that should be contained only in scatterlist.h.
We replace these with calls to sg_chain and sg_assign_page.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
Cc: Dan Williams
Cc: Vinod Koul
Cc: Linus Walleij
---
On Sun, May 21, 2017 at 11:42:23AM +0800, Ryder Lee wrote:
> Hi,
>
> This patch series add Mediatek Gen2 PCIe host controller driver and
> dt-binding document. It can be found on MT7623 series SoCs.
>
> This driver was validated using Broadcom Tigon3 and Intel(R) 82575/82576
> gigabit ethernet ca
On Wed, May 24, 2017 at 02:29:16PM -0700, Jarkko Sakkinen wrote:
> The memory copy from rodata to stack is useless.
>
> Signed-off-by: Jarkko Sakkinen
I already applied this, reviewed-by would be nice for this one but given
how obvious this change is, it is not mandatory. I take my chances on
th
On Wed, May 24, 2017 at 02:24:11PM +0200, Michal Hocko wrote:
20b2f52b73fe ("numa: add CONFIG_MOVABLE_NODE for movable-dedicated
node") has introduced CONFIG_MOVABLE_NODE without a good explanation on
why it is actually useful. It makes a lot of sense to make movable node
semantic opt in but we a
On Wed, May 24, 2017 at 02:24:10PM +0200, Michal Hocko wrote:
74d42d8fe146 ("memory_hotplug: ensure every online node has NORMAL
memory") has added can_offline_normal which checks the amount of
memory in !movable zones as long as CONFIG_MOVABLE_NODE is disable.
It disallows to offline memory if t
IO memory support can be indicated by an iteratee with the
SG_MITRE_SUPPORTS_IOMEM flag. If an unmappable sgl gets into a miter
without this support, the kernel will BUGON.
For supported cases, the sg_miter code will set the ioaddr pointer and
leave addr NULL.
sg_copy_buffer is changed to support
This is a layering violation so we replace it with calls to
sg_page. This is a prep patch for replacing page_link and this
is one of the very few uses outside of scatterlist.h.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
drivers/staging/ccree/ssi_buffer_mgr.c | 17 --
Convert all uses of bv_page to bvec_page and bvec_set page as introduced
in the previous patch.
This is mostly done with the following coccinelle script plus some
additional fussing by hand.
@@
expression bv;
expression x;
@@
-bv->bv_page = x;
+bvec_set_page(bv, x);
@@
expression bv;
expression
This is incomplete but is given to test the unmappable sg page code.
Further work would actually use p2p memory in the rdma target. (One
should imagine something vaguely resembling our original p2pmem RFC[1]
being on top of this.)
We convert to using an unmappable sgl in the rdma nvme target drive
Two dma engine drivers directly accesses page_link assuming knowledge
that should be contained only in scatterlist.h.
We replace these with calls to sg_chain and sg_assign_page.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
drivers/dma/imx-dma.c | 7 ++-
drivers/dma/ste
Introduce two accessor functions for bv_page: bvec_page to return the
page and bvec_set_page. A follow on patch will mechanically convert all the
individual uses within the kernel.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
include/linux/bvec.h | 10 ++
1 file chang
This patch replaces the old page_link bits with the somewhat safer
pfn_t. This change seems to have been planned for in the design of pfn_t
by Dan.
The conversion is surprisingly straightforward. sg_assign_pfn and
sg_set_pfn helpers are added which are similar analogs to their
page_link versions.
Going straight from pfn_t to physical address is cheaper and
avoids the potential BUG_ON in bvec_page for unmappable memory.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
include/linux/bio.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/lin
Introduce sg_try_virt which is safe to call with a potentially
unmappable sgl. sg_try_virt returns NULL in cases that the sgl doesn't
have an accessible virtual address to return.
Then, in dma_map_sg_attrs, we use the new function instead of sg_virt
when marking memory as initialized.
Signed-off-
This is a layering violation so we replace the uses with calls to
sg_page(). This is a prep patch for replacing page_link and this
is one of the very few uses outside of scatterlist.h.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
samples/kfifo/dma-example.c | 8
1 fi
With bv_page fenced off, we can now convert it to a pfn_t fairly simply.
Everything should work the same with the exception of a BUG_ON
for potentially unmappable pfns.
A couple of initializers that assign {NULL} to a bio_vec had to also be
changed to {} to prevent a warning seeing pfn_t is actual
We introduce bio_add_pfn which is the same as bio_add_page but expects a
pfn_t instead of a page pointer. bio_add_page is then converted to be
an inline call to bio_add_pfn.
Signed-off-by: Logan Gunthorpe
Signed-off-by: Stephen Bates
---
block/bio.c | 16
include/linu
Going through bvec_page and sg_set_page now implies a conversion
to and then from a struct page as well as a potential unnecessary BUG_ON
check. Instead we go directly from bv_pfn to sg_set_pfn.
This is done easily with the following coccinelle patch:
@@
expression sg;
expression bv;
expression l
Add a default ioremap function which was not provided in all
circumstances. (Only when CONFIG_PCI and CONFIG_TILEGX was set).
I have designs to use them in scatterlist.c where they'd likely never
be called with this architecture, but it is needed to compile.
Signed-off-by: Logan Gunthorpe
Signed
Hi,
This RFC patchset continues my work attempting to enforce iomem safety
within scatterlists. This takes a bit of a different tack from my
last series [1] which tried to introduce a common scatterlist mapping
function. Instead, this series takes the approach of marking SGLs that
may contain unma
The user mode architecture does not provide ioremap or iounmap, and
because of this, the arch won't build when the functions are used in some
core libraries.
I have designs to use these functions in scatterlist.c where they'd
almost certainly never be called on the um architecture but it does need
This patch introduces the PFN_MAYBE_UNMAPPABLE flag which indicates the
sgl or pfn may point to unmappable memory. This flag would be set by a
call to sg_init_unmappable_table which sets the flag for all entries in
the table. Once set, any attempt to call sg_page, sg_virt, etc on the sgl
will BUG_O
On Fri, May 19, 2017 at 02:58:55PM -0500, Bjorn Helgaas wrote:
> PCI_STD_RESOURCE_END is (confusingly) the index of the last valid BAR, not
> the *number* of BARs. To iterate through all possible BARs, we need to
> include PCI_STD_RESOURCE_END.
>
> Fixes: 9fe373f9997b ("PCI: Increase IBM ipr SAS
On Sun, Apr 30, 2017 at 07:49:21PM +1200, Michael Schmitz wrote:
> get_reg() can be reentered on architectures with prioritized interrupts
> (m68k in this case), causing f->reg_index to be incremented after the
> range check. Out of bounds memory access past the pt_regs struct results.
> This will
On Fri, May 19, 2017 at 02:56:06PM -0500, Bjorn Helgaas wrote:
> pci_add_resource_offset() is for host bridge windows where the bridge
> translates CPU addresses to PCI bus addresses by adding an offset. To my
> knowledge, no host bridge translates bus numbers, so this is only useful
> for MEM and
Implement the request_locality function. To set the locality on the
backend we define vendor-specific TPM 1.2 and TPM 2 ordinals and send
a command to the backend to set the locality for the next commands.
To avoid recursing into requesting the locality, we set the
TPM_TRANSMIT_RAW flag when calli
e pushed
out two new branches based on linux-next tag next-20170524, one is just the
driver-data API [0], and the other one just has this patch applied on top
of the driver-data API [1]. You'll want to use driver-data-stable if you are
working on the cache or the fallback mechanism since t
Introduce the flag TPM_TRANSMIT_RAW that allows us to transmit
a command without recursing into the requesting of locality.
Signed-off-by: Stefan Berger
Reviewed-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 3 ++-
drivers/char/tpm/tpm.h | 1 +
2 files changed, 3 insertio
201 - 300 of 1118 matches
Mail list logo
