archive mirror
 help / color / mirror / Atom feed
From: Rajat Jain <>
To: Mika Westerberg <>
Cc: Rajat Jain <>,
	Andreas Noever <>,
	Michael Jamet <>,
	Yehezkel Bernat <>,,
	Linux Kernel Mailing List <>,
	Greg KH <>
Subject: Re: [PATCH v3] thunderbolt: For dev authorization changes, include the actual event in udev change notification
Date: Mon, 2 Aug 2021 11:49:44 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <YQgKIok9DOTgmyvw@lahna>

On Mon, Aug 2, 2021 at 8:07 AM Mika Westerberg
<> wrote:
> Hi Rajat,
> On Fri, Jul 30, 2021 at 04:53:04PM -0700, Rajat Jain wrote:
> > For security, we would like to monitor and track when the thunderbolt
> > devices are authorized and deauthorized (i.e. when the thunderbolt sysfs
> > "authorized" attribute changes). Currently the userspace gets a udev
> > change notification when there is a change, but the state may have
> > changed (again) by the time we look at the authorized attribute in
> > sysfs. So an authorization event may go unnoticed. Thus make it easier
> > by informing the actual change (new value of authorized attribute) in
> > the udev change notification.
> >
> > The change is included as a key value "authorized=<val>" where <val>
> > is the new value of sysfs attribute "authorized", and is described at
> > Documentation/ABI/testing/sysfs-bus-thunderbolt under
> > /sys/bus/thunderbolt/devices/.../authorized
> >
> > Signed-off-by: Rajat Jain <>
> I did some tiny changes to the title, commit message and the comment and
> applied to thunderbolt.git/next, thanks!

Thank you!


      reply	other threads:[~2021-08-02 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 23:53 [PATCH v3] thunderbolt: For dev authorization changes, include the actual event in udev change notification Rajat Jain
2021-08-02 15:07 ` Mika Westerberg
2021-08-02 18:49   ` Rajat Jain [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).