linux-kernel - [RFC PATCH v1 0/3] mm/PM/USB: memory allocation with no io in need

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1350403183-12650-1-git-send-email-ming.lei@canonical.com>
Date:	Tue, 16 Oct 2012 23:59:40 +0800
From:	Ming Lei <ming.lei@...onical.com>
To:	linux-kernel@...r.kernel.org
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oneukum@...e.de>,
	Minchan Kim <minchan@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-pm@...r.kernel.org
Subject: [RFC PATCH v1 0/3] mm/PM/USB: memory allocation with no io in need

Hi,

This patch set introduces one process flag and trys to fix one deadlock
problem on block device during runtime resume or usb bus reset.

The 1st one is the change on include/sched.h and mm.

The other 2 patches are applied again PM and USB subsystem to demo
how to use the introduced mechanism to fix the deadlock problem.

V1:
        - take Minchan's change to avoid the check in alloc_page hot path
	- change the helpers' style into save/restore as suggested by Alan
	- memory allocation with no io in usb bus reset path for all devices
	as suggested by Greg and Oliver


 drivers/base/power/runtime.c |   14 ++++++++++++++
 drivers/usb/core/hub.c       |   11 +++++++++++
 include/linux/sched.h        |   11 +++++++++++
 mm/page_alloc.c              |   10 +++++++++-
 mm/vmscan.c                  |   13 +++++++++++++
 5 files changed, 58 insertions(+), 1 deletion(-)

Thanks,
--
Ming Lei

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/