The patch titled nbd: use task_pid_nr() to get current pid has been added to the -mm tree. Its filename is nbd-use-task_pid_nr-to-get-current-pid.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: nbd: use task_pid_nr() to get current pid From: WANG Cong <amwang@xxxxxxxxxx> Signed-off-by: WANG Cong <amwang@xxxxxxxxxx> Cc: Paul Clements <Paul.Clements@xxxxxxxxxxxx> Cc: Jens Axboe <axboe@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/block/nbd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/block/nbd.c~nbd-use-task_pid_nr-to-get-current-pid drivers/block/nbd.c --- a/drivers/block/nbd.c~nbd-use-task_pid_nr-to-get-current-pid +++ a/drivers/block/nbd.c @@ -405,7 +405,7 @@ static int nbd_do_it(struct nbd_device * BUG_ON(lo->magic != LO_MAGIC); - lo->pid = current->pid; + lo->pid = task_pid_nr(current); ret = sysfs_create_file(&disk_to_dev(lo->disk)->kobj, &pid_attr.attr); if (ret) { printk(KERN_ERR "nbd: sysfs_create_file failed!"); _ Patches currently in -mm which might be from amwang@xxxxxxxxxx are linux-next.patch drm-add-missing-header-file-linuc-typesh.patch nbd-use-task_pid_nr-to-get-current-pid.patch nbd-replace-sysfs_create_file-with-device_create_file.patch nbd-replace-printk-kern_err-with-dev_err.patch nbd-lower-the-loglevel-of-an-error-message.patch nbd-replace-some-printk-with-dev_warn-and-dev_info.patch nbd-some-trivial-improvements.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html