Hi
I think the idea is fine.
There is architecture problem - that target specific routines are being
pushed into generic dm core.
I suggest that instead of dm_send_verity_uevent and dm_path_uevent you
create just one generic function (for example dm_send_uevent) that takes
variable argument
Hi
I think the idea is fine.
There is architecture problem - that target specific routines are being
pushed into generic dm core.
I suggest that instead of dm_send_verity_uevent and dm_path_uevent you
create just one generic function (for example dm_send_uevent) that takes
variable argument
On Thu, Jun 20, 2013 at 10:00 PM, Geremy Condra wrote:
> With this change dm-verity errors will cause uevents to be
> sent to userspace, notifying it that an error has occurred
> and potentially triggering recovery actions.
>
> Signed-off-by: Geremy Condra
> ---
> Changelog since v1:
> - Removed
On Thu, Jun 20, 2013 at 10:00 PM, Geremy Condra gcon...@google.com wrote:
With this change dm-verity errors will cause uevents to be
sent to userspace, notifying it that an error has occurred
and potentially triggering recovery actions.
Signed-off-by: Geremy Condra gcon...@google.com
---
With this change dm-verity errors will cause uevents to be
sent to userspace, notifying it that an error has occurred
and potentially triggering recovery actions.
Signed-off-by: Geremy Condra
---
Changelog since v1:
- Removed the DM_VERITY_ERROR_NOTIFY config option
drivers/md/dm-uevent.c | 40
With this change dm-verity errors will cause uevents to be
sent to userspace, notifying it that an error has occurred
and potentially triggering recovery actions.
Signed-off-by: Geremy Condra gcon...@google.com
---
Changelog since v1:
- Removed the DM_VERITY_ERROR_NOTIFY config option
6 matches
Mail list logo