From: Ivajlo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: <gregkh@linuxfoundation.org>
Cc: "Ивайло Димитров" <freemangordon@abv.bg>,
pali.rohar@gmail.com, sre@ring0.de, pavel@ucw.cz,
omar.ramirez@copitl.com, tony@atomide.com,
felipe.contreras@gmail.com, s-anna@ti.com, nm@ti.com,
ohad@wizery.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Staging: tidspbridge: disable driver
Date: Sat, 30 Nov 2013 11:58:23 +0200 [thread overview]
Message-ID: <6662B6F95D1C4783A007CAC82A8DA641@ivogl> (raw)
Hi,
(re-sending in plain text, sorry for the noise)
commit
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=930ba4a374b96560ef9fde2145cdc454a164ddcc
disables tidspbridge driver for the reasons it has a security bug and there
is no active maintainer.
I was following the development of that driver for a bit and my impression
was that the reason it is
still in staging is this
http://www.spinics.net/lists/linux-omap/msg84115.html . And as dmtimer
driver is on its way to be merged upstream(or was it already merged?) I was
planning to work on
tidspbridge driver to fix it and send the patches. I also have a couple of
another small patches
ready to be send.
However, could you elaborate on the "security bug" so I can try to fix it
and send the patch?
Also, what needs to be done for the tidspdriver to get out of staging as it
seems that what I
though initially is incorrect.
Regards,
Ivo
PS: my further mails will be from this account on gmal as it seems LKML does
not like
my abv.bg account (freemangordon at abv dot bg)
next reply other threads:[~2013-11-30 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 9:58 Ivajlo Dimitrov [this message]
2013-11-30 16:20 ` Greg KH
2013-11-30 17:27 ` Tony Lindgren
2013-11-30 19:19 ` Pavel Machek
2013-11-30 19:49 ` Dan Carpenter
2013-11-30 20:42 ` [patch] Staging: tidspbridge: make mmap root-only so it is not a security problem Pavel Machek
2013-11-30 22:05 ` Greg KH
2013-11-30 22:58 ` Pavel Machek
2013-12-01 3:45 ` Greg KH
2013-12-01 9:47 ` Pali Rohár
2013-12-01 11:26 ` Pavel Machek
2013-12-01 11:33 ` Pali Rohár
2013-12-01 9:41 ` Pali Rohár
2013-12-01 9:58 ` Ивайло Димитров
2013-12-01 12:10 ` Pavel Machek
2013-12-01 12:27 ` Dan Carpenter
2013-12-01 18:14 ` Ivajlo Dimitrov
2013-12-01 18:57 ` Pavel Machek
2013-12-01 19:28 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6662B6F95D1C4783A007CAC82A8DA641@ivogl \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=freemangordon@abv.bg \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ohad@wizery.com \
--cc=omar.ramirez@copitl.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=s-anna@ti.com \
--cc=sre@ring0.de \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®