On 06/12/2013 08:28 AM, Bart Van Assche wrote:
> + /*
> + * It can occur that after fast_io_fail_tmo expired and before
> + * dev_loss_tmo expired that the SCSI error handler has
> + * offlined one or more devices. scsi_target_unblock() doesn't
> +
On Wed, Jun 19, 2013 at 12:15:53PM -0700, Joe Perches wrote:
> Don't emit OOM warnings when k.alloc calls fail when
> there there is a v.alloc immediately afterwards.
>
> Signed-off-by: Joe Perches
For fs/ext4/super.c:
Acked-by: "Theodore Ts'o"
- Ted
--
Once stop_machine() is gone from the CPU offline path, we won't be able
to depend on disabling preemption to prevent CPUs from going offline
from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
offline, while invoking from atomic context.
Cc: Hoang-Nam Nguyen
Cc: C