Re: MPC5200b jffs2 memcpy alignment problem

Hi Albrecht, > I don't recall who proposed this patch, but exactly this solution is > around for a longer time (mayby you search archives...). On my board, I > have a flash chip attached to the LocalBus in 16-bit mode. Based on > 3.2.16, the patch is: Thanks for your answer and yes, this patch

Re: [RFC PATCH 10/12] memory-hotplug : free memmap of sparse-vmemmap

On 06/27/2012 01:56 PM, Yasuaki Ishimatsu wrote: > I don't think that all pages of virtual mapping in removed memory can be > freed, since page which type is MIX_SECTION_INFO is difficult to free. > So, the patch only frees page which type is SECTION_INFO at first. > > CC: Len Brown > CC: Benjami

Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages

On 06/27/2012 01:44 PM, Yasuaki Ishimatsu wrote: > When offline_pages() is called to offlined memory, the function fails since > all memory has been offlined. In this case, the function should succeed. > The patch adds the check function into offline_pages(). > > CC: Len Brown > CC: Benjamin Herr

Re: [RFC PATCH 2/12] memory-hogplug : check memory offline in offline_pages

On 06/27/2012 01:44 PM, Yasuaki Ishimatsu wrote: > When offline_pages() is called to offlined memory, the function fails since > all memory has been offlined. In this case, the function should succeed. > The patch adds the check function into offline_pages(). > > CC: Len Brown > CC: Benjamin Herr

Re: MPC5200b jffs2 memcpy alignment problem

Hi Stephan: Am 30.06.12 21:16 schrieb(en) Stephan Gatzka: I have a problem running jffs2 on an MPC5200b board. I run kernel 3.4, but older kernels like 3.1.5 are also affected. Every time I mount jffs2, previously written content gets garbled. The problem was nailed down to memcpy(&fd->name,

MPC5200b jffs2 memcpy alignment problem

Hello! First of all, please apologize my cross posting. I have a problem running jffs2 on an MPC5200b board. I run kernel 3.4, but older kernels like 3.1.5 are also affected. Every time I mount jffs2, previously written content gets garbled. The problem was nailed down to memcpy(&fd->name, r

[PATCH -v5 1/6] fault-injection: notifier error injection

The notifier error injection provides the ability to inject artifical errors to specified notifier chain callbacks. It is useful to test the error handling of notifier call chain failures. This adds common basic functions to define which type of events can be fail and to initialize the debugfs in

[PATCH -v5 0/6] notifier error injection

This provides kernel modules that can be used to test the error handling of notifier call chain failures by injecting artifical errors to the following notifier chain callbacks. * CPU notifier * PM notifier * memory hotplug notifier * powerpc pSeries reconfig notifier Example: Inject CPU offl

[PATCH -v5 6/6] fault-injection: add selftests for cpu and memory hotplug

This adds two selftests * tools/testing/selftests/cpu-hotplug/on-off-test.sh is testing script for CPU hotplug 1. Online all hot-pluggable CPUs 2. Offline all hot-pluggable CPUs 3. Online all hot-pluggable CPUs again 4. Exit if cpu-notifier-error-inject.ko is not available 5. Offline all hot-plug

[PATCH -v5 5/6] powerpc: pSeries reconfig notifier error injection module

This provides the ability to inject artifical errors to pSeries reconfig notifier chain callbacks. It is controlled through debugfs interface under /sys/kernel/debug/notifier-error-inject/pSeries-reconfig If the notifier call chain should be failed with some events notified, write the error code