summaryrefslogtreecommitdiff
BranchCommit messageAuthorAge
aarch64/hotplug-vcpu/headACPI: Add _OSC bits to advertise OS support for toggling CPU present/enabledJames Morse5 months
aarch64/hotplug-vcpu/v6.5cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse10 months
aarch64/hotplug-vcpu/v6.6ACPI: processor: Only call arch_unregister_cpu() if HOTPLUG_CPU is selectedJames Morse8 months
aarch64/hotplug-vcpu/v6.6-rc1cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse10 months
aarch64/hotplug-vcpu/v6.6-rc5cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse9 months
aarch64/hotplug-vcpu/v6.6-rc6ACPI: processor: Only call arch_unregister_cpu() if HOTPLUG_CPU is selectedJames Morse8 months
aarch64/hotplug-vcpu/v6.6-rc7ACPI: processor: Only call arch_unregister_cpu() if HOTPLUG_CPU is selectedJames Morse8 months
aarch64/hotplug-vcpu/v6.7cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse6 months
aarch64/hotplug-vcpu/v6.7-rc1cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse8 months
aarch64/hotplug-vcpu/v6.7-rc2cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse7 months
aarch64/hotplug-vcpu/v6.7-rc3cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse7 months
aarch64/hotplug-vcpu/v6.7-rc4cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse7 months
aarch64/hotplug-vcpu/v6.7-rc5cpumask: Add enabled cpumask for present CPUs that can be brought onlineJames Morse7 months
aarch64/hotplug-vcpu/v6.8-rc2ACPI: Add _OSC bits to advertise OS support for toggling CPU present/enabledJames Morse5 months
aarch64/ktext/headarm64: text replication: verify kernel textRussell King (Oracle)6 months
aarch64/ktext/v6.5arm64: text replication: verify kernel textRussell King (Oracle)9 months
aarch64/ktext/v6.6-rc5arm64: text replication: verify kernel textRussell King (Oracle)9 months
aarch64/ktext/v6.7arm64: text replication: verify kernel textRussell King (Oracle)6 months
adfsfs/adfs: bigdir: Fix an error code in adfs_fplus_read()Dan Carpenter4 years
cex7Revert "iommu: silence iommu group prints"Russell King5 weeks
clearfogarm64: dts: add SolidRun CN9130 Clearfog Base dtsRussell King (Oracle)5 weeks
clearfog-4.10ARM: dts: armada388-clearfog: document MPP usageRussell King7 years
clearfog-4.11sfp: removal of defsRussell King7 years
clearfog-4.12implement slot capabilities (SSPL)Russell King7 years
clearfog-4.13implement slot capabilities (SSPL)Russell King7 years
clearfog-4.9ARM: dts: armada388-clearfog: document MPP usageRussell King7 years
clkdevARM: 8778/1: clkdev: don't call __of_clk_get_by_name() unnecessarily from clk...Bartosz Golaszewski6 years
csi-v6media: fix VIDEO_DEV dependenciesRussell King6 weeks
devel-stableMerge tag 'arm-vfp-refactor-for-rmk' of git://git.kernel.org/pub/scm/linux/ke...Russell King (Oracle)12 months
drm-armada-develARM: dts: cubox: add LCD controller and TDA998x configurationRussell King8 months
drm-armada-devel-4.15drm/armada: expand overlay trace entryRussell King7 years
drm-armada-fixesLinux 5.1Linus Torvalds5 years
drm-armada-fixes-4.15drm/armada: fix YUV planar format framebuffer offsetsRussell King7 years
drm-dwhdmi-develLinux 4.14-rc1Linus Torvalds7 years
drm-etnaviv-develdrm: etnaviv: try harder to reset the GPU at probe timeRussell King8 years
drm-tda9950-fixesdrm/i2c: tda9950: set MAX_RETRIES for errors onlyHans Verkuil6 years
drm-tda998x-develdrm/i2c: tda998x: add support for writing SPDRussell King8 months
drm-tda998x-fixesLinux 5.1Linus Torvalds5 years
fec-testingnet: fec: try better napi packet processing algorithmRussell King10 years
fiqARM: cobble together FIQ backtracingRussell King3 years
fixesARM: 9405/1: ftrace: Don't assume stack frames are contiguous in memoryArd Biesheuvel3 weeks
fixes-sa1111ARM: sa1111: fix missing clk_disable()Russell King8 years
for-arm-socLinux 5.10-rc1Linus Torvalds4 years
for-nextMerge branches 'clkdev', 'fixes' and 'misc' into for-nextRussell King (Oracle)3 weeks
hb2Linux 4.16-rc1Linus Torvalds6 years
ktextarm64: text replication: verify kernel textRussell King (Oracle)8 months
ktext-currentarm64: text replication: verify kernel textRussell King (Oracle)9 months
masterLinux 6.10-rc3Linus Torvalds4 weeks
mcbinDont-Auto-BuildRussell King5 weeks
mvnetaLinux 5.3Linus Torvalds5 years
mvpp2Linux 5.6Linus Torvalds4 years
net-mergednet: stmmac: dwmac-intel: remove checking for fixed linkRussell King (Oracle)5 weeks
net-nextnet: dsa: remove obsolete phylink dsa_switch operationsRussell King (Oracle)5 weeks
net-queuenet: dsa: mv88e6xxx: add 6352 family EEE supportRussell King (Oracle)5 weeks
nmiARM: add basic support for on-demand backtrace of other CPUsRussell King9 years
phynet: sfp: display SFP module information [*not for mainline*]Russell King4 years
rtcrtc: armada38x: provide set_offset_nsecRussell King6 weeks
sa1100ipaq sleeve updatesRussell King3 months
spectreARM: fix the cockup in the previous patchRussell King6 years
to-buildnet: sfp: avoid tx-fault with Nokia GPON moduleRussell King5 years
uaccessARM: uaccess: fix DACR mismatch with nested exceptionsRussell King4 years
wl18xxnet: wlcore: debugfs: export information on queued firmware framesRussell King (Oracle)6 weeks
ziinet: dsa: debugging printsRussell King5 weeks
 
TagDownloadAuthorAge
for-linuscommit 594ce0b8a9...Russell King (Oracle)3 weeks
amba-for-coresightcommit aff0042757...Krzysztof Kozlowski3 months
for-airlie-armadacommit 837567c1e9...Russell King5 years
for-airlie-tda998xcommit 45a19dd397...Russell King5 years
for-rc-adfscommit fc722a0429...Russell King5 years
for-4.21commit 6de92920a7...Russell King6 years
generated by cgit (git 2.34.1) at 2024-07-04 16:05:54 +0000
bers of 'struct multipath'Mike Snitzer The use of atomic_t for nr_valid_paths, pg_init_in_progress and pg_init_count will allow relaxing the use of the m->lock spinlock. Suggested-by: Hannes Reinecke <hare@suse.de> Reviewed-by: Hannes Reinecke <hare@suse.com> Tested-by: Hannes Reinecke <hare@suse.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> 2016-05-05dm mpath: switch to using bitops for state flagsMike Snitzer Mechanical change that doesn't make any real effort to reduce the use of m->lock; that will come later (once atomics are used for counters, etc). Suggested-by: Hannes Reinecke <hare@suse.de> Reviewed-by: Hannes Reinecke <hare@suse.com> Tested-by: Hannes Reinecke <hare@suse.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> 2016-05-05dm thin: Remove return statement from void functionAmitoj Kaur Chawla Return statement at the end of a void function is useless. The Coccinelle semantic patch used to make this change is as follows: //<smpl> @@ identifier f; expression e; @@ void f(...) { <... - return e; ...> } //</smpl> Signed-off-by: Amitoj Kaur Chawla <amitoj1606@gmail.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> 2016-05-05dm: remove unused mapped_device argument from free_tio()Mike Snitzer Signed-off-by: Mike Snitzer <snitzer@redhat.com> 2016-05-04md-cluster: fix ifnullfree.cocci warningskbuild test robot drivers/md/bitmap.c:2049:6-11: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid passing NULL values. NULL check before some freeing functions is not needed. Based on checkpatch warning "kfree(NULL) is safe this check is probably not required" and kfreeaddr.cocci by Julia Lawall. Generated by: scripts/coccinelle/free/ifnullfree.cocci Acked-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster/bitmap: unplug bitmap to sync dirty pages to diskGuoqing Jiang This patch is doing two distinct but related things. 1. It adds bitmap_unplug() for the main bitmap (mddev->bitmap). As bit have been set, BITMAP_PAGE_DIRTY is set so bitmap_deamon_work() will not write those pages out in its regular scans, only bitmap_unplug() will. If there are no writes to the array, bitmap_unplug() won't be called, so we need to call it explicitly here. 2. bitmap_write_all() is a bit of a confusing interface as it doesn't actually write anything. The current code for writing "bitmap" works but this change makes it a bit clearer. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster/bitmap: fix wrong page num in bitmap_file_clear_bit and ↵Guoqing Jiang bitmap_file_set_bit The pnum passed to set_page_attr and test_page_attr should from 0 to storage.file_pages - 1, but bitmap_file_set_bit and bitmap_file_clear_bit call set_page_attr and test_page_attr with page->index parameter while page->index has already added node_offset before. So we need to minus node_offset in both bitmap_file_clear_bit and bitmap_file_set_bit. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster/bitmap: fix wrong calcuation of offsetGuoqing Jiang The offset is wrong in bitmap_storage_alloc, we should set it like below in bitmap_init_from_disk(). node_offset = bitmap->cluster_slot * (DIV_ROUND_UP(store->bytes, PAGE_SIZE)); Because 'offset' is only assigned to 'page->index' and that is usually over-written by read_sb_page. So it does not cause problem in general, but it still need to be fixed. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: sync bitmap when node received RESYNCING msgGuoqing Jiang If the node received RESYNCING message which means another node will perform resync with the area, then we don't want to do it again in another node. Let's set RESYNC_MASK and clear NEEDED_MASK for the region from old-low to new-low which has finished syncing, and the region from old-hi to new-hi is about to syncing, bitmap_sync_with_cluste is introduced for the purpose. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: always setup in-memory bitmapGuoqing Jiang The in-memory bitmap for raid is allocated on demand, then for cluster scenario, it is possible that slave node which received RESYNCING message doesn't have the in-memory bitmap when master node is perform resyncing, so we can't make bitmap is match up well among each nodes. So for cluster scenario, we need always preserve the bitmap, and ensure the page will not be freed. And a no_hijack flag is introduced to both bitmap_checkpage and bitmap_get_counter, which makes cluster raid returns fail once allocate failed. And the next patch is relied on this change since it keeps sync bitmap among each nodes during resyncing stage. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: wakeup thread if activated a spare diskGuoqing Jiang When a device is re-added, it will ultimately need to be activated and that happens in md_check_recovery, so we need to set MD_RECOVERY_NEEDED right after remove_and_add_spares. A specifical issue without the change is that when one node perform fail/remove/readd on a disk, but slave nodes could not add the disk back to array as expected (added as missed instead of in sync). So give slave nodes a chance to do resync. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: change array_sectors and update size are not supportedGuoqing Jiang Currently, some features are not supported yet, such as change array_sectors and update size, so return EINVAL for them and listed it in document. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: fix locking when node joins cluster during message broadcastGuoqing Jiang If a node joins the cluster while a message broadcast is under way, a lock issue could happen as follows. For a cluster which included two nodes, if node A is calling __sendmsg before up-convert CR to EX on ack, and node B released CR on ack. But if a new node C joins the cluster and it doesn't receive the message which A sent before, so it could hold CR on ack before A up-convert CR to EX on ack. So a node joining the cluster should get an EX lock on the "token" first to ensure no broadcast is ongoing, then release it after held CR on ack. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: unregister thread if err happenedGuoqing Jiang The two threads need to be unregistered if a node can't join cluster successfully. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: wake up thread to continue recoveryGuoqing Jiang In recovery case, we need to set MD_RECOVERY_NEEDED and wake up thread only if recover is not finished. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluser: make resync_finish only called after pers->sync_requestGuoqing Jiang It is not reasonable that cluster raid to release resync lock before the last pers->sync_request has finished. As the metadata will be changed when node performs resync, we need to inform other nodes to update metadata, so the MD_CHANGE_PENDING flag is set before finish resync. Then metadata_update_finish is move ahead to ensure that METADATA_UPDATED msg is sent before finish resync, and metadata_update_start need to be run after "repeat:" label accordingly. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-04md-cluster: change resync lock from asynchronous to synchronousGuoqing Jiang If multiple nodes choose to attempt do resync at the same time they need to be serialized so they don't duplicate effort. This serialization is done by locking the 'resync' DLM lock. Currently if a node cannot get the lock immediately it doesn't request notification when the lock becomes available (i.e. DLM_LKF_NOQUEUE is set), so it may not reliably find out when it is safe to try again. Rather than trying to arrange an async wake-up when the lock becomes available, switch to using synchronous locking - this is a lot easier to think about. As it is not permitted to block in the 'raid1d' thread, move the locking to the resync thread. So the rsync thread is forked immediately, but it blocks until the resync lock is available. Once the lock is locked it checks again if any resync action is needed. A particular symptom of the current problem is that a node can get stuck with "resync=pending" indefinitely. Reviewed-by: NeilBrown <neilb@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> 2016-05-02Merge tag 'md/4.6-rc6-fix' of ↵Linus Torvalds git://git.kernel.org/pub/scm/linux/kernel/git/shli/md Pull MD fixes from Shaohua Li: "This update includes several trival fixes. The only important one is to fix MD bio merge, which has big performance impact" * tag 'md/4.6-rc6-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/shli/md: raid5: delete unnecessary warnning MD: make bio mergeable md/raid0: remove empty line printk from dump_zones md/raid0: fix uninitialized variable bug